Skip to content

Troubleshooting

Diagnosis and resolution for common Azure Monitor issues.

graph TD
    A[Symptom] --> B[Architecture Overview]
    B --> C[Mental Model]
    C --> D{Decision Tree}
    D -->|No Data| E[Data Playbooks]
    D -->|Alert Issues| F[Alert Playbooks]
    D -->|Cost Issues| G[Cost Playbook]
    D -->|Performance| H[Slow Query Playbook]
    E & F & G & H --> I[KQL Queries]
    I --> J[Resolution]

Start Here

Use these entry pages in order when you need fast routing before opening a detailed playbook.

Need Go To
Understand where Azure Monitor can fail end to end Architecture Overview
Use a symptom → hypothesis → validation workflow Mental Model
Route from symptom to the right playbook quickly Decision Tree
Know which evidence sources to collect first Evidence Map

Quick Navigation

Symptom Go To
Data not appearing in workspace No Data in Workspace
Application Insights not showing telemetry Missing Application Telemetry
Alert rule not firing Alert Not Firing
Too many alerts Alert Storm
Unexpected cost spike High Ingestion Cost
KQL queries timing out Slow Query Performance
Agent not sending data Agent Not Reporting

In This Section

Page Description
Architecture Overview Azure Monitor troubleshooting map: sources, routing, stores, and consumers
Mental Model Symptom → hypothesis → validation framework for investigations
Decision Tree Symptom-based routing to playbooks
Evidence Map What data sources to check for each symptom
Playbooks Step-by-step troubleshooting guides (9 playbooks)
KQL Query Packs Ready-to-use diagnostic queries (14 pages)

Suggested Flow

  1. Read Architecture Overview to identify the likely failure domain.
  2. Use Mental Model to list competing hypotheses before making changes.
  3. Route with the Decision Tree.
  4. Open the targeted playbook and collect KQL and CLI evidence.

See Also

Sources