Loading
Tech stack
Logs, metrics, traces, correlation IDs, Application Insights, OpenTelemetry, incident triage, alerting, runbooks, and production debugging workflows.
Practice items tagged with Observability and Production Incidents.
Explains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.
Chooses heap-focused GC evidence or complete process state based on memory growth, roots, hangs, crashes, locks, and collection risk.
Compares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.
Chooses counters, traces, stack snapshots, GC dumps, full dumps, or a profiler from the production symptom and investigation cost.
Designs controlled diagnostic access, collection triggers, container permissions, artifact egress, privacy, retention, and post-capture verification.
Compares vendor-neutral OpenTelemetry concepts with Application Insights usage for .NET production services.
Preparation paths where this taxonomy appears in the track scope.
Prove API behavior, reproduce failures, and leave durable regression evidence.
A practical ASP.NET Core track covering authenticated integration tests, capability and ownership boundaries, ProblemDetails, idempotent retries, stable pagination, cancellation, concurrency, database command guards, correlated failures, distributed tracing, connection-pool pressure, health checks, incident regressions, and post-deploy smoke checks.
Logs, metrics, traces, alerts, triage, mitigation, and post-incident learning.
A practical production-ownership track covering observability foundations, correlation IDs, structured logs, dependency telemetry, OpenTelemetry, health checks, sampling, incident triage, slow API diagnosis, post-release failures, downstream dependency incidents, missing logs, queue backlogs, auth failures, SLO alerts, dashboards, release correlation, mitigation choices, post-incident reviews, runbooks, and capacity/backpressure signals.