Loading
Technology
Vendor-neutral observability instrumentation for traces, metrics, logs, context propagation, exporters, and service telemetry.
Practice items tagged with OpenTelemetry.
Separates application composition in AppHost from reusable in-process defaults for telemetry, health, resilience, and service discovery.
Explains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.
Compares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.
Compares vendor-neutral OpenTelemetry concepts with Application Insights usage for .NET production services.
Explains sampling, high-cardinality labels, retention, cost, and keeping enough signal for incident diagnosis.
Explains deployment markers, version telemetry, feature-flag state, commit traceability, and incident diagnosis after releases.
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.