Any event that may lead to a disruption in your organization’s services can be described as an incident, and it is often necessary to have a set framework for handling these events. Datadog’s Incident Management feature provides a system through which your organization can effectively identify and mitigate incidents.
Incidents live in Datadog alongside the metrics, traces, and logs you are collecting. You can view and filter incidents that are relevant to you.
In the Datadog paradigm, any of the following are appropriate situations for declaring an incident:
Incident Management requires no installation. To view your incidents, go to the Incidents page for a feed of all ongoing incidents. You can configure additional fields that appear for all incidents in Incident Settings.
You can declare an incident directly from a graph. You can also go to the upper right hand side of the Incidents page and click on “New Incident”. The following dialog box appears.
Severity: Denotes the severity of your incident, from SEV-1 (most severe) to SEV-5 (least severe). If your incident is under initial investigation, and you do not know the severity yet, select UNKNOWN.
Title: Give your incident a descriptive title.
Signals: The reason(s) you are declaring the incident. These can be graphs, logs, or other key visuals.
Incident commander: This person is assigned as the leader of the incident investigation.
Additional notifications: Notify other teams or people.
Click on “Declare Incident” to finish creating your incident.
Consider a scenario in which you are looking at a dashboard, and you notice that one particular service is showing an especially high error count. Using the Export button in the upper right of a widget, you can declare an incident.
Use the New Incident modal to assemble your team and notify them. The graph from which you created the incident is automatically attached as a signal. Attach any other signals that would give your team the necessary context to begin resolving this issue. The Slack and PagerDuty integrations enable you to send notifications through those services.
If you have the Datadog Slack app installed, the Slack integration can automatically create a new channel dedicated to the incident, so you can consolidate communication with your team and begin troubleshooting.
For non-EU customers who use Slack, sign up for beta access to the Datadog Slack app. For EU customers who use Slack, stay informed about the Slack app by emailing email@example.com.
Update the incident as the situation evolves. Set the status to
Stable to indicate the problem has been mitigated, and set the customer impact field so that your organization knows how this issue has affected customers. Then, set the status to
Resolved once the incident is completely fixed. There is an optional fourth status,
Completed, that can be used to track if all remediation steps are complete. This status can be enabled in Incident Settings.
You can update the status and severity in the
Properties section of each incident.
As the status of an incident changes, Datadog tracks time-to-resolution as follows:
|Status Transition||Resolved Timestamp|
|Overridden on last transition|
Link to a postmortem document, look back on exactly what went wrong, and add follow-up tasks. Postmortems created in Datadog Notebooks support live collaboration; to link to an existing notebook, click the plus under
Other Docs. Click the linked notebook to edit with teammates in real-time.