
Open
Posted
•
Ends in 2 days
Title: Azure Observability Engineers Needed: Splunk to Azure Migration (Remote, Jan–May 2027) Description: We’re building an Azure-native observability platform for a large international organization and moving it off Splunk. We’re looking for experienced freelance engineers to join a small remote team. Project: Remote, Jan–May 2027, with possible extension into ongoing support. Working hours need to overlap Central European Time (CET). We need skills in one or more of these areas: 1) Azure observability: Azure Monitor, Log Analytics, KQL, Terraform 2) Splunk migration: SPL, Splunk Observability Cloud, converting dashboards and alerts 3) Grafana dashboards: KQL, PromQL, Prometheus 4) Synthetic monitoring: Playwright, k6, Docker
Project ID: 40798903
18 proposals
Open for bidding
Remote project
Active 1 day ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs
18 freelancers are bidding on average ₹1,177 INR/hour for this job

Hi, I’m interested in exploring this remote observability project. We can discuss how our development team could support the Azure-native monitoring setup and migration activities. The key areas of focus would include Azure Monitor, Log Analytics, KQL, Terraform, Grafana dashboards, monitoring automation, and synthetic testing with Playwright and k6. I’d like to understand a few details: Are you looking for dedicated engineers for individual skill areas or engineers covering multiple areas? Is the migration already underway, or will the selected team handle the initial assessment and migration planning? What level of CET overlap and weekly availability do you require? Let's connect on chat to discuss the requirements and potential collaboration
₹1,000 INR in 40 days
7.3
7.3

Hi, We’ve migrated monitoring from Splunk to Azure-native stacks. For one client, we rebuilt dashboards and alerts in Azure Monitor and Grafana with Terraform. Alert noise dropped, and the team ran fully on Azure without losing visibility. We’d cover the full set: Azure Monitor and Log Analytics with KQL, SPL-to-KQL conversion of dashboards and alerts, Grafana dashboards (KQL, PromQL, Prometheus), and synthetic monitoring with Playwright and k6 in Docker. We’d overlap CET hours and are available January to May 2027, with extension for ongoing support. Proposal: ₹2,500/hr per engineer. The posted ₹750-1,250 is below market for this skill set. A 2-engineer team is about 320 hours a month. How large is the Splunk estate (dashboards, alerts and data sources)? SolutionzHere
₹2,500 INR in 40 days
6.0
6.0

Hi, I am a Senior Cloud and DevOps Engineer with 16+ years of experience in Azure, AWS, infrastructure automation, monitoring, and production environments. I can contribute to your Splunk-to-Azure observability migration by helping design and implement an Azure-native monitoring platform. My experience includes Azure Monitor, Log Analytics, KQL, Terraform, Prometheus, Grafana, Docker, and CI/CD automation. I can assist with migrating monitoring configurations, converting logs and alerts, developing Grafana dashboards, implementing infrastructure through Terraform, and setting up centralized logging, metrics, and actionable alerts. I can also support synthetic monitoring and performance testing using tools such as Playwright and k6. My focus will be on building a scalable, reliable, and maintainable observability solution with proper documentation and validation throughout the migration. I’m interested in the remote engagement from January to May 2027 and can discuss working-hour overlap with CET. I’m available for a technical discussion to understand the project requirements and team expectations. Best regards, Sahil
₹1,200 INR in 40 days
5.3
5.3

I can contribute to the Azure-native observability migration, particularly around Azure Monitor, Log Analytics, KQL, Terraform and Grafana. I’d approach it in stages: assess existing Splunk dashboards and alerts, map SPL logic to KQL, rebuild monitoring and alerting, then validate coverage before cutover. My proposed rate is ₹2,250/hour, with availability and CET overlap agreed upfront. I’m also comfortable working remotely with a distributed engineering team through the January–May 2027 delivery window. Which workstream needs the most support initially: Azure/KQL, Splunk conversion, Grafana, or synthetic monitoring?
₹2,250 INR in 40 days
4.9
4.9

Hi, I have 10 years of experience in DevOps and cloud infrastructure, including Azure, Terraform, monitoring, and observability. I can contribute to building Azure-native monitoring and dashboards, with a focus on reliable deployment, clear alerting, and practical documentation. I’m available for the Jan–May 2027 engagement and can arrange working-hour overlap with CET. I’d be glad to discuss which workstream best matches your immediate needs. Could you share the expected weekly hours and whether the role is focused primarily on Azure Monitor/KQL, Splunk migration, Grafana, or synthetic monitoring? Best regards Rahul
₹1,200 INR in 40 days
3.4
3.4

Hi, I'm Karthik, an Azure Observability Engineer with over 15 years of experience in cloud technologies and observability solutions. I am excited about the opportunity to assist in migrating your observability platform from Splunk to Azure, and I believe my extensive background aligns perfectly with your project's requirements. Key Skills: - Azure Observability: Proficient in Azure Monitor, Log Analytics, and KQL. I have successfully implemented observability solutions that enhance performance and reliability. - Splunk Migration: Hands-on experience with SPL and the Splunk Observability Cloud, including converting dashboards and alerts to Azure-native formats. - Grafana Dashboards: Skilled in developing and optimizing dashboards using KQL, PromQL, and Prometheus, ensuring insightful visualizations for stakeholders. - Synthetic Monitoring: Experienced in utilizing tools like Playwright, k6, and Docker for effective synthetic monitoring. I am available to work remotely from January to May 2027, with flexible hours to ensure overlap with CET. I'm committed to delivering high-quality results and providing ongoing support if needed. Let’s discuss how I can contribute to building your Azure-native observability platform! Best regards, Karthik
₹1,330 INR in 40 days
5.0
5.0

My AWS-certified cloud and DevOps background, together with Azure, Terraform, Docker, Grafana, Prometheus, Datadog and ELK Stack expertise, aligns strongly with your Azure-native observability migration. I can contribute across infrastructure automation, monitoring platforms, dashboards and containerized observability workloads while your team moves away from Splunk. I also work with CloudWatch and broader cloud architecture, giving me practical experience with logs, metrics and operational visibility in scalable environments. Terraform supports repeatable infrastructure delivery, while Grafana and Prometheus experience maps well to dashboarding and metrics-focused monitoring. My full-stack and backend development background further helps connect observability requirements with the applications and services being monitored. I would be a strong addition to your remote team for the January–May 2027 engagement and any continuing support. Choose me to bring cloud engineering, monitoring and infrastructure-as-code skills to this migration.
₹1,000 INR in 40 days
2.4
2.4

Hi, there. Recently migrated a global financial institution's Splunk estate (15TB/day) to Azure Monitor/Log Analytics using Terraform modules and KQL, cutting ingestion costs 40% while standardizing detection logic across 200+ workspaces. I engineered a SPL-to-KQL transpiler pipeline using Python/AST parsing to automate dashboard/alert conversion, resolving parsing ambiguities in complex `stats`/`eval` chains and `join` operations by mapping them to optimized KQL `join`/`union` strategies with materialized views. I offer a phased migration framework: Terraform-driven workspace provisioning with RBAC/Linked Storage, automated SPL conversion validated via CI/CD regression testing against production traffic shadows, and Grafana dashboard provisioning via KQL datasource using Jsonnet templating. Synthetic coverage is implemented via Playwright/k6 containers deployed to ACI, feeding custom metrics into Log Analytics via Data Collection Rules for unified alerting. If I use my previous experience, your project will likely be completed successfully. Hope to discuss this in detail. Through detailed discussion, I think I can find the better solution to finish your project successfully. Thank you
₹1,000 INR in 40 days
0.0
0.0

Hi, a move from Splunk to Azure Monitor and Log Analytics that keeps the alerts people actually rely on. Rewriting SPL as KQL is mechanical. Matching thresholds and noise is where these go wrong. How we would do it: rank the Splunk dashboards and saved searches by real usage, rebuild workspaces and alert rules in Terraform, then run each converted alert beside its Splunk original until the counts match. Grafana covers the PromQL views, k6 checks run from Docker. Which of the four areas is most urgent for you? We can overlap CET hours through May. Happy to start on a small batch of dashboards first. Regards, Digitalizers
₹750 INR in 40 days
0.0
0.0

Hi, We can support your Azure-native observability migration by helping transition monitoring, dashboards, and alerts from Splunk to Azure while maintaining visibility and reliability throughout the process. Our approach: - Configure Azure Monitor and Log Analytics, using KQL for querying and analysis. - Use Terraform to provision and manage observability infrastructure consistently. - Review Splunk SPL queries, dashboards, and alerts, then plan their migration to Azure-native tools. - Build Grafana dashboards using KQL or Prometheus data sources where appropriate. - Support synthetic monitoring with Playwright or k6, containerised with Docker. - Document configurations, validate results, and support a smooth handover. We can align with your remote team and CET overlap requirements during the January–May 2027 engagement. A few questions: 1. Which workstream is your immediate priority: Azure observability, Splunk migration, Grafana, or synthetic monitoring? 2. What is the current Splunk environment and approximate volume of dashboards and alerts? 3. Are Azure subscriptions, access permissions, and Terraform repositories already in place? 4. What CET working-hour overlap and weekly availability do you require? Let’s connect to discuss the scope, team requirements, and engagement milestones. Note: The actual quote might vary on the final scope. Regards, Agnidipa Team Qloron
₹1,000 INR in 40 days
0.0
0.0

Hi, I’m Md Shahid Ansari, a full‑stack developer and AI/DevOps engineer with 2+ years of freelance experience delivering end‑to‑end cloud solutions. I’ll migrate your Splunk workloads to Azure by recreating dashboards and alerts in Azure Monitor / Log Analytics using KQL, and I’ll codify the infrastructure with Terraform for repeatable deployments. My recent project “Finance LLM Translator” required Docker containers, FastAPI, and cloud hosting, so I’m comfortable setting up Docker‑based synthetic monitors with Playwright or k6 and integrating them into Azure pipelines. I’ve also built data pipelines and performed extensive data analysis, which helps me translate SPL queries into efficient KQL statements while preserving alert logic. My work schedule can overlap CET, and I’m ready to start in January. Looking forward to helping your team build a robust Azure observability platform.
₹1,000 INR in 40 days
0.0
0.0

Hello, The core challenge lies in mapping complex SPL logic and data schemas into optimized KQL queries without losing granularity or increasing query latency during the transition. I will begin by auditing existing Splunk data models and alerting rules to establish a baseline for parity in Azure Monitor. I will use Terraform to deploy standardized Log Analytics workspaces, ensuring environment consistency across environments. The migration strategy focuses on refactoring heavy joins into performant KQL-based views and validating data integrity before final cutover. You will receive a fully migrated Azure-native observability stack, documented KQL-based dashboards, and a repeatable IaC pipeline for future infrastructure scaling. I have executed multiple large-scale Splunk-to-Azure migrations for enterprise-level telemetry data. I can start immediately. Regards.
₹1,000 INR in 40 days
0.0
0.0

Hi, I am a Colombia-based engineer (UTC-5, so my mornings overlap your CET afternoons every working day). Observability is part of my daily work running production Kubernetes and AWS platforms: Grafana with PromQL and Prometheus, alerting and SLOs, log analytics with Loki and CloudWatch, synthetic monitoring with Playwright and k6, and Terraform. Two ways I can contribute: Option A - Dashboards, alerts and synthetic monitoring track: rebuild the migrated dashboards and alerts in Grafana and Azure Monitor (KQL and PromQL data sources), and build Playwright/k6 synthetic checks with alert routing. Option B - Broader role: Option A plus Log Analytics workspace design, KQL alert rules and Terraform modules, working with your Splunk specialists on the SPL-to-KQL translation. This is how monitoring fits into the layered production architecture I run: https://www.freelancer.com/portfolio-items/13573784-secure-layered-cloud-architecture Happy to do a short technical call. Roughly how many dashboards and alerts are being migrated?
₹800 INR in 20 days
0.0
0.0

Title: Azure Observability Engineers Needed: Splunk to Azure Migration (Remote, Jan–May 2027) Description: We’re building an Azure-native observability platform for a large international organization and moving it off Splunk. We’re looking for experienced freelance engineers to join a small remote team. Project: Remote, Jan–May 2027, with possible extension into ongoing support. Working hours need to overlap Central European Time (CET). We need skills in one or more of these areas: 1) Azure observability: Azure Monitor, Log Analytics, KQL, Terraform 2) Splunk migration: SPL, Splunk Observability Cloud, converting dashboards and alerts 3) Grafana dashboards: KQL, PromQL, Prometheus 4) Synthetic monitoring: Playwright, k6, Docker
₹1,000 INR in 40 days
0.0
0.0

Hi, I would join for your area 3: Grafana dashboards with PromQL and Prometheus, including converting dashboards and alerts during the move off Splunk. What I bring: - I wrote open-source Prometheus exporters in Python that ship with Grafana dashboards and 29 alert rules, and they run in production. - I monitor 18 bare-metal servers and 40+ LXC containers with Prometheus, Grafana and Alertmanager, with central logs in Loki, Graylog and ELK. - I package services with Docker and Docker Compose, which also helps with the synthetic monitoring tooling in area 4. How I would approach the conversion: 1. List the existing dashboards and alerts, and agree what question each one answers, so nothing gets copied without a reason. 2. Rebuild them in Grafana with variables and reusable templates, so the team can maintain them. 3. Run new alerts side by side with the old ones and compare them before cutover. 4. Document each dashboard and alert for the support phase. Availability: January to May 2027, remote, up to 20 hours a week. I am in Pakistan, so I can overlap with CET afternoons. Two questions: how many dashboards and alerts are in scope for the first phase, and will the Grafana panels read mainly from Prometheus or from Azure Monitor?
₹1,150 INR in 20 days
0.0
0.0

Chennai, India
Member since Nov 16, 2021
₹750-1250 INR / hour
₹750-1250 INR / hour
₹1250-2500 INR / hour
₹1250-2500 INR / hour
$30-250 USD
₹75000-150000 INR
$50 USD
₹1000000-2500000 INR
$10-30 USD
$30-250 USD
$10-30 USD
$250-750 USD
₹12500-37500 INR
₹12500-37500 INR
₹600-1500 INR
$8-15 USD / hour
$5000-10000 USD
$8-15 USD / hour
$750-1500 USD
₹12500-37500 INR
$250-750 USD
$250-750 USD
$150-200 USD
₹600-1500 INR