Solve incidents faster with All Quiet
Incidents
. Per Default, it shows all open
incidents of your teams.
Urgency
. You can change this to Latest interaction
, Created
or Title
by clicking on Urgency
.
Open
or Resolved
Critical
, Warning
or Minor
open
incidents with severity Warning
from team My First Team
and integration Datadog PROD
:
title
and attributes
. Just write what you’re looking for in the text field Search in title and attributes
and hit ENTER to see the resulting incidents.
Hide Snoozed
to Include Snoozed
or Only Snoozed
, the incident overview will display snoozed incidents as well / solely, identified by a Snooze symbol.
Unsnooze the incident to inform your on-call colleagues about this incident.
Incidents
in the sidebar of the Web App.+ Create Incident
.Status
for the incident.Severity
.Title
.Team
you want to create the incident in. After creation, on-call team members will be notified. If you selected an Organization in step 4, you can select (No Team)
, but than have to assign the incident to at least one specific user in step 7.Inbound Integration
. If it’s a general incident that isn’t realted to any integration, select (No Integration)
or All Quiet
.Critical
to Warning
. Once you’ve made your choice, simply save your changes.
Resolve
button. This will notify all colleagues of the current escalation tier that the incident was resolved. Always stops any auto-escalations.Investigate
button. This will notify all colleagues of the current escalation tiers that you’re investigating the issue. It will also mark the incident as acknowledged. Auto-escalations are stopped if your settings say “Stop Auto-Escalation” if “Incident is acknowledged”.Escalate
button. This will notify all colleagues of the current escalation tiers as well as the following escalation tier. This action re-initiates / sustains auto-escalations.Comment
.
resolved
. For more info, see section Reopening Incidents.Public
flag.forward
single incidents to your team’s Outbound Integrations. First, click “Forward”.
Forward
button if you activated the Triggers Only On Forwarded
feature for at least one Outbound Integration. Else, we will automatically forward incidents to your outbound integrations. The setup can defined in each integration’s details page.Forward
in the incidents details view, you can select the outbound integration you want to forward the issue to. Incidents can always be forwarded, even after they are resolved.
Affects
action, you can easily connect incidents with your services and status pages, allowing you semlessly share downtime and incident updates with your customers, allowing you to fully focus on fixing the issue whilst having everyone onboard.
After clicking Affects
in the incidents details view, an overlay opens.
Affect
.Public
flag.
Cloud Infrastructure
.Assign
action to assign an incident to teams, specific users, or both.
After clicking Assign
in the incident’s detail view, an overlay will open.
Assign
button, you will see all teams in your organization. Select the teams you want to assign the incident to. You can either add teams to the currently assigned ones or reassign the incident to entirely different teams.Assign
to reassign the incident to the selected team(s). All involved on-call members of the all assigned teams will be notified about the incident.Assign to User
action, you can notify them anytime.
Assign
to reassign the incident to the selected users(s). The selected user(s) will be notified about the inciden, no matter if they are on-call or not.not acknowledged
, and escalations either start (if snoozed via integration settings) or continue (if manually snoozed).archive
incidents. Archiving incidents does not change their resolution state, only moves them from the incidents overview to the archive.
Archive
IntentUnarchived
. Then, they will be visible on the incidents overview, again.Reopen
button on a resolved incident.
You can also add a comment.
Reopening an incident will inform the current Tier 1 on-call users of the involved teams. It will also restart the auto-escalations of the involved team(s).
Created
, Tier 1 members are alerted and, if configured in your on-call schedule, auto-escalations start.
After somebody Investigates
, Comments
, Snoozes
, Archives
or Resolves
an incident, is gets marked as acknowledged.
If your settings stop auto-escalations if incident is acknowledged, any potential auto-escalations are stopped. If your settings stop auto-escalations if incident is resolved, any potential auto-escalations are only stopped if somebody Resolves
an incident.
For a previously acknowledged incident, Escalating
, Reopening
, Unsnoozing
or Assigning
it to a new / extra team / person re-marks the incident as not acknowledged and reactivates any potential auto-escalations.
The actions Affects
, Forward
and Unarchive
have no influence on the current acknowledgement state and, therefore, on your auto-escalations.
isGroupingKey
here.
Once set up, incidents with matching values for the defined grouping key attributes will be grouped.
On the incident overview, grouped incidents can be identified by a little label that includes a count of the number of incidents grouped in this incident.
isGroupingKey
in the incident mapping of the integration. As long as the incident group remains open, any new incidents matching the defined criteria (e.g., attribute UTM
= 333) will be added to the group. Exception: When using groupingWindowInSeconds, new incidents will only be grouped as long as they are created within the defined groupingWindowInSeconds
. After the window has ended, incidents will create new groups and alert your on-call colleagues again.