ObservabilityIntermediate12 submodules

Azure Monitor and Application Observability

Collect, correlate, query, visualize, alert, and test Azure platform and application telemetry using Azure Monitor, Log Analytics, Application Insights, and KQL.

From concept to production evidence

Instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Learning outcomes

  • Explain metrics, logs, traces, and tests
  • Configure Azure Monitor and Log Analytics
  • Instrument Application Insights
  • Write KQL queries
  • Create alerts, action groups, workbooks, dashboards, and availability tests

Azure Monitor and Application Observability end-to-end flow

Use this sequence as the operating backbone for every submodule note and hands-on exercise.

  1. 01
    Emit telemetryAzure Monitor and Application Observability stage 1: emit telemetry with an auditable result before the next stage begins.
  2. 02
    Collect and correlateAzure Monitor and Application Observability stage 2: collect and correlate with an auditable result before the next stage begins.
  3. 03
    Store workspace dataAzure Monitor and Application Observability stage 3: store workspace data with an auditable result before the next stage begins.
  4. 04
    Query with KQLAzure Monitor and Application Observability stage 4: query with kql with an auditable result before the next stage begins.
  5. 05
    Visualize healthAzure Monitor and Application Observability stage 5: visualize health with an auditable result before the next stage begins.
  6. 06
    Alert and respondAzure Monitor and Application Observability stage 6: alert and respond with an auditable result before the next stage begins.

Observe an Azure application journey

  1. Enable platform diagnostics
  2. Instrument application traces
  3. Write KQL for a critical request
  4. Build workbook and alert
  5. Create availability test and action group

12 full submodule notes

Read in order
01

Azure Monitor

Azure Monitor turns service behavior into evidence that supports detection, diagnosis, capacity decisions, and measurable reliability within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
02

Log Analytics

Log Analytics turns service behavior into evidence that supports detection, diagnosis, capacity decisions, and measurable reliability within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
03

Application Insights

Application Insights provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
04

Metrics

Metrics turns service behavior into evidence that supports detection, diagnosis, capacity decisions, and measurable reliability within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
05

Logs

Logs turns service behavior into evidence that supports detection, diagnosis, capacity decisions, and measurable reliability within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
06

Alerts

Alerts turns service behavior into evidence that supports detection, diagnosis, capacity decisions, and measurable reliability within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
07

Action Groups

Action Groups provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
08

Workbooks

Workbooks turns service behavior into evidence that supports detection, diagnosis, capacity decisions, and measurable reliability within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
09

Dashboards

Dashboards turns service behavior into evidence that supports detection, diagnosis, capacity decisions, and measurable reliability within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
10

KQL

KQL turns service behavior into evidence that supports detection, diagnosis, capacity decisions, and measurable reliability within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
11

Distributed tracing

Distributed tracing provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes
12

Availability tests

Availability tests turns service behavior into evidence that supports detection, diagnosis, capacity decisions, and measurable reliability within Azure Monitor and Application Observability. It is not an isolated definition: its value appears when it supports instrument around user journeys and service objectives, separate metrics, logs, and traces, centralize queries, alert on actionable symptoms, route through owned action groups, and validate externally with availability tests.

Open full notes