Incident Investigation View Explained

Incident investigation view is split into two components; Deployment History Graph and Details Summary Panel.

With the Incident Investigation View, you can track changes leading up to, or during an incident. You can investigate all the deployments and past incidents, both on your impacted and related services. This way, you'll be able to identify problematic changes that might have caused the incident.

To use the Incident Investigation View, select the components on the Deployment History Graph, and view the information on the Details Summary Panel. If you think its relevant, select commits, or a whole deployment as a potential cause of the incident.

Deployment History Graph

The Deployment History Graph is where you can see all changes and other incidents that occurred on your impacted services and related services. Each impacted service has its deployment track within the history chart.

The timeframe is 24 hours by default, where at most 1 hour after the incident creation is shown, and the remaining time is the time leading up to the incident creation. You may toggle back and forth different time segments using the filter options, and you may change the default time range from 24 hours to 48 hours or a week.

Additionally, you can filter deployments shown on the graph by using the Environment dropdown. The dropdown shows all the environments in which deployments are made and available to be shown on the graph.

You can expand the Deployment History Graph to show the tracks of all related services. To do that, select the expansion button, which is on the left of the impacted service list, on the impacted services panel.

Expanding the impacted service reveals the related services, which include the depending services and contained services as per your configuration of service relations. You can also see the tracks of the related services within the history chart.

Icons used on the history chart

  • Successful deployments - The green node represents a successful deployment related to the service, consisting of changes originating from repositories.
    • File changes - The file changes are represented by a shade surrounding the deployment nodes. This represents the number of files changed, or attempted to be changed, depending on the deployment was successful or failed.
    • Failed deployments - This node indicates that a failed deployment occurred on the repositories related to the service that the node appears.
    • Grouped deployments - Shows deployments that have occurred in consecutive order so that they cannot be visualized on the graph separately. Select a shorter time range to reveal deployments separately.
    • Contains potential causes - Appears on top of the deployment nodes and helps keep track which deployments are selected as potential causes, or have commits selected as potential causes.
    • Other Incidents - Refers to the past incidents or other ongoing incidents on the services they appear on.
    • Incident marker - Indicates the time on the history chart the incident was created, after which all tracks relating to impacted services are represented in red.

Details Summary Panel

The deployments and commits that are selected on the Deployment History Graph are displayed in this section. The information on this panel are;

  • Deployment details summary - Details of all deployment information and commits included in a selected deployment.
  • Service details summary - Details of service information including related services and past incidents.
  • Incident details summary - Details of the incident, such as responders, incident priority, and various information giving an overall context of the incident.

Updated 25 days ago


Incident Investigation View Explained


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.