Layer 6 · Session 55 · Planned · Not validated
Correlation IDs and distributed request tracing
An authoring contract, not a completed lesson.
Status: Planned. Validation and personal walkthrough not started. Not published.
Purpose
Introduce correlation ids and distributed request tracing because the workload needs a new decision or capability.
Learning objectives
- Explain the model in workload context.
- Compare responsibility and cost tradeoffs.
- Apply it through a reproducible CLI-first exercise.
- Verify and clean up.
Concepts planned
Definition, architecture connection, purposeful visual, prediction, comparison, and fact/recommendation labels.
Expected lab outcome
One observable, independently verified change with cost, security, reliability, and operational effects.
Prerequisites and continuity
Previous: Session 54 — Metrics, logs, traces, and events. Next: Session 56 — Alerts, dashboards, and action groups.
Author notes
- Check official Microsoft docs.
- Add explicit scope, variables, verification, cleanup, and cost.
- Execute in disposable resources and record environment/date.
- Test failure paths and update architecture.
Do not teach from this page yet. It stays unhydrated until tested.