investigate

Incident investigation correlates signals from Sentry, Prometheus, Loki, Kibana, and Nomad to identify root causes by cross-referencing metrics, logs, and traces within a unified workflow.

Yes, cross-source diagnostics query Prometheus metrics and Loki logs simultaneously, correlating events across monitoring and logging platforms to surface the likely root cause of production symptoms.

Incident workflow alignment performs service health checks, gathers correlated evidence across Sentry, Prometheus, and Kibana, and produces a formal incident report to ensure post-mortem readiness.

No, symptom-driven workflows start from user-reported symptoms without a known root cause, applying cross-source analysis to work toward actionable remediation plans with human-in-the-loop validation.

Cross-source diagnostics correlate Sentry error tracking with Nomad deployment events, aligning production incident practices to connect application errors with infrastructure changes.

Describe the incident symptoms and time window, then trigger the cross-source investigation command to initiate a full analysis across Sentry, Prometheus, Loki, Kibana, and Nomad.