AZ-204 — Application observability

Route position

This path closes the AZ-204 application loop. It follows runtime, data, identity, and integration and teaches how an application exposes evidence for diagnosis and availability decisions.

Ordered modules

  1. Instrument, query, and alert on application behavior.

Core mental model

Instrumentation emits telemetry; collection stores it; queries interpret it; alert rules evaluate signals; action groups route a response. Metrics summarize numeric behavior, logs preserve structured records, and traces connect a request across components. None of these proves the workload is healthy unless the signal measures a meaningful user or service outcome.

Checkpoint

Given a failed API request, identify whether metrics, logs, or traces provide the fastest evidence; trace the signal into an alert rule and action group; and explain how an availability test differs from internal application telemetry.

Sources and re-audit

Re-audit when telemetry, query, availability-test, or alert behavior changes.