> Markdown version of [/jobs/ext/4688242-observability-analyst-azure-monitor-grafana](https://www.wearedevelopers.com/jobs/ext/4688242-observability-analyst-azure-monitor-grafana). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Observability Analyst (Azure Monitor / Grafana) - **Company:** Jobot - **Location:** Fort Worth, TX, United States - **Experience:** Expert - **Salary:** $90,000 - $105,000 - **Contract:** Permanent contract - **Skills:** Agile Methodology, Database Queries, Information Technology Operations, Python (Programming Language), Operational Data Store, Windows PowerShell, Kusto Query Language, SQL Databases, Grafana, Mttr - **Published:** November 12, 2026 - **Apply:** https://www.dice.com/job-detail/83159b51-1370-4282-8164-f146fcbce340 ## About the Role 4+ years in IT operations, monitoring and alerting, incident management, systems administration, or operational analysis and reporting Hands-on incident management experience (triage, RCA, post-incident reviews) Experience with Azure Monitor and Grafana or similar observability tools Comfort writing queries (KQL or SQL) and an interest in scripting and automation Clear communication with technical and non-technical audiences Pluses: ITIL, Microsoft, or CompTIA certs; PowerShell or Python; Agile; financial services experience; a bachelor's in IT, CS, or analytics ## Description The Senior Operations Analyst turns operational data into insight about service health. You'll connect logs, alerts, monitoring signals, incidents, and support cases to find patterns, reduce noise, and surface reliability risk before it turns into an outage. What you'll do: Analyze log, alert, and monitoring data in Azure Monitor and Grafana to find recurring issues, anomalies, noise, and coverage gaps Design and maintain dashboards, scorecards, and recurring reports for technical teams and leadership Support incident triage, coordination, communications, timelines, root cause analysis, and post-incident reviews, and track MTTR, severity, and recurrence Track SLIs, SLOs, and error budget burn, and tie reliability trends back to incidents, bugs, and support cases Correlate defects and support work items with operational data to sharpen prioritization Write telemetry queries, update runbooks, validate alerts, and build approved scripts and automations that cut manual effort Turn loosely defined requirements into structured analysis and clear recommendations