Loading
Pick a focused question that fits your time, stack, and interview goal.
27 results across 1 active filter
Page 1 of 2
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.
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.
Explains what belongs in runbooks, how on-call handoff preserves context, and how operational docs stay useful.
Explains how to troubleshoot absent logs or telemetry by checking configuration, sampling, sinks, levels, deployment, and correlation.
Explains alert design based on user-impact symptoms, SLOs, burn rate, thresholds, and avoiding noisy cause-only alerts.
Explains dashboard panels that help an API owner see user impact, dependency health, releases, and current incidents.
Explains health checks that prove an API can serve traffic without becoming fragile dependency probes.
Explains a telemetry-driven path from slow endpoint symptoms to database, cache, dependency, CPU, or payload root cause.
Collects a bounded EventPipe CPU trace and reads stack evidence without confusing hot methods, blocked time, native work, or sampling artifacts.
Explains initial incident triage: confirm impact, mitigate, assign roles, preserve evidence, and communicate.
Explains how to triage post-release 500 errors using deployment correlation, logs, traces, feature flags, and rollback safety.
Explains how to diagnose 401/403 spikes across token validation, identity provider issues, clock skew, deployment changes, and abuse.
Explains correlation IDs across request logs, dependency calls, queues, workers, and support investigations.
Combines ThreadPool counters, repeated stack snapshots, and wait-event traces to distinguish blocked workers from CPU or dependency pressure.
Uses live runtime and application counters to classify CPU, memory, GC, exception, request, and ThreadPool symptoms before deeper collection.
Explains how to diagnose and mitigate a downstream dependency slowing the API through timeouts, retries, and degraded behavior.
Explains how to investigate queue age, backlog, worker health, poison messages, dependency failures, and safe catch-up.
Explains post-incident review, root cause, contributing factors, action items, tests, alerts, runbooks, and ownership.