incident-triage

To build an incident timeline, you correlate errors, deploys, and metrics from multiple data sources into a coherent chronological trace. This process speeds resolution by showing when errors began, what deployments occurred, and how metrics changed.

Correlating deployment events with errors and metrics involves pulling data from VCS deploy logs, error trackers, and metrics dashboards. This approach assembles a timeline showing the relationship between recent deployments and performance degradations or outages.

Yes, you can use incident triage for postmortems across systems and services. It gathers deterministic data from multiple sources to produce a comprehensive timeline, helping you analyze production outages and performance degradations after they occur.

To start an incident triage session, initiate the process to collect related signals from your connected data sources. It will automatically gather logs, metrics, and deploy data to construct a clear timeline of the performance degradation.

No, incident triage requires no external dependencies or components to function. It uses built-in capabilities for data gathering, canvas contextualization, and memory persistence to investigate incidents without needing additional setup.