Skip to content

Commit f22306e

Browse files
[DOCS-10343] Event Management Inbox (#30836)
* Event Mgmt Inbox * formatting updates * fix typos * adding screenshot and video * updating landing page * Apply suggestions from code review Co-authored-by: Esther Kim <[email protected]> * suggestions from Esther's review * Move Triage Inbox under Event mgmt * Remove file from PR * Fix link formats --------- Co-authored-by: Esther Kim <[email protected]>
1 parent 8230080 commit f22306e

File tree

5 files changed

+77
-5
lines changed

5 files changed

+77
-5
lines changed

config/_default/menus/main.en.yaml

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2651,26 +2651,31 @@ menu:
26512651
identifier: event_explorer_saved_views
26522652
parent: events_explorer
26532653
weight: 308
2654+
- name: Triage Inbox
2655+
identifier: event_triage_inbox
2656+
url: service_management/events/triage_inbox
2657+
parent: events
2658+
weight: 4
26542659
- name: Correlation
26552660
url: service_management/events/correlation/
26562661
identifier: event_correlation
26572662
parent: events
2658-
weight: 4
2663+
weight: 5
26592664
- name: Configuration
26602665
url: service_management/events/correlation/configuration
26612666
identifier: event_correlation_configure
26622667
parent: event_correlation
2663-
weight: 401
2668+
weight: 501
26642669
- name: Triaging & Notifying
26652670
url: service_management/events/correlation/triage_and_notify
26662671
identifier: event_correlation_triage_and_notify
26672672
parent: event_correlation
2668-
weight: 402
2673+
weight: 502
26692674
- name: Analytics
26702675
url: service_management/events/correlation/analytics
26712676
identifier: event_correlation_analytics
26722677
parent: event_correlation
2673-
weight: 403
2678+
weight: 503
26742679
- name: Guides
26752680
url: service_management/events/guides/
26762681
identifier: events_guides

content/en/service_management/events/_index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ further_reading:
3131

3232
Ingest, enrich and normalize, and correlate your events from any source into actionable insights. Datadog automatically creates events from various products including monitors, Watchdog, and Error Tracking. You can also track events generated from the Agent and installed integrations. Event Management can also ingest events from any source, including alert events from third parties, change requests, deployments, configuration changes.
3333

34-
More than 100 Datadog integrations support events collection, including [Kubernetes][1], [Docker][2], [Jenkins][3], [Chef][4], [Puppet][5], [Amazon ECS][6] or [Autoscaling][7], [Sentry][8], and [Nagios][9].
34+
More than 100 Datadog integrations support events collection, including [Kubernetes][1], [Docker][2], [Jenkins][3], [Chef][4], [Puppet][5], [Amazon ECS][6] or [Autoscaling][7], [Sentry][8], and [Nagios][9].
3535

3636
**Tip**: To open the Event Management page from Datadog's global search, press <kbd>Cmd</kbd>/<kbd>Ctrl</kbd> + <kbd>K</kbd> and search for `event explorer`.
3737

@@ -41,6 +41,7 @@ More than 100 Datadog integrations support events collection, including [Kuberne
4141

4242
{{< whatsnext desc="Event Management features:">}}
4343
{{< nextlink href="/service_management/events/ingest/" >}}<u>Ingest events</u> - Learn how to send events to Datadog{{< /nextlink >}}
44+
{{< nextlink href="/service_management/events/triage_inbox" >}}<u>Triage Inbox</u> - Triage, investigate, collaborate, and resolve incidents{{< /nextlink >}}
4445
{{< nextlink href="/service_management/events/pipelines_and_processors/">}}<u>Pipelines and Processors</u> - Enrich and Normalize your events{{< /nextlink >}}
4546
{{< nextlink href="/service_management/events/explorer/" >}}<u>Events Explorer</u> - View, search and send notifications from events coming into Datadog{{< /nextlink >}}
4647
{{< nextlink href="/service_management/events/guides/usage/" >}}<u>Using events</u> - Analyze, investigate, and monitor events {{< /nextlink >}}
Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
title: Event Management Triage Inbox
3+
further_reading:
4+
- link: "/service_management/events/ingest//"
5+
tag: "doc"
6+
text: "Send events to Datadog"
7+
- link: "/service_management/events/correlation/"
8+
tag: "doc"
9+
text: "Learn more about event correlation"
10+
- link: "https://www.datadoghq.com/blog/datadog-event-management/"
11+
tag: "Blog"
12+
text: "Aggregate, correlate, and act on alerts faster with AIOps-powered Event Management"
13+
---
14+
15+
## Overview
16+
17+
Datadog Event Management [Triage Inbox][4] simplifies incident response by consolidating related events from any source into actionable cases. This centralized view reduces noise and helps teams triage, investigate, and collaborate more effectively. With customizable saved views, you can stay focused on high-priority cases and review correlated alerts, related changes, and telemetry, all in one place.
18+
19+
## Triaging and investigating cases
20+
21+
Case triage and investigation begins in the Triage Inbox, where you can sort, filter, and manage incoming cases. Collaborate with teammates, both within and outside of Datadog, to coordinate responses. From there, you can prioritize, assign, investigate, and escalate cases as needed to drive faster resolution.
22+
23+
{{< img src="/service_management/events/triage_inbox/event_mgmt_inbox.mp4" alt="Event Management Inbox, sorting by priority, highlighting changing status and priority capabilities" video=true >}}
24+
25+
## Getting Started
26+
27+
1. Navigate to [**Service Management** > **Event Management** > **Triage Inbox**][4].
28+
2. Select a project from the left-hand panel to display out-of-the-box status views such as **Open**, **In Progress**, **Closed**, and **Archived**.
29+
3. Use the display settings icon to choose between **split view** (for detailed case investigation) or **table view** (for bulk case review and column configuration). Customize your inbox ranking with the **Sort By** dropdown-options include **Priority**, **Created at**, or **Last Updated**. Click **Save** to re-use your customized inbox for future use.
30+
5. Update the status, priority, and assignment directly on case cards during triage.
31+
6. Maximize screen space by collapsing the left-hand case project panel and the Datadog navigation bar.
32+
7. Hover over the case card **alert** count to preview correlated alerts.
33+
34+
## Next Steps
35+
36+
Now that you've learned how to triage and investigate cases, use these tools to [collaborate](#collaborate-and-integrate) with your team, [take action](#take-action) on root causes, and streamline response efforts.
37+
38+
## Collaborate and Integrate
39+
40+
On the right hand split-view side panel, you can perform the following:
41+
42+
- **Tag and comment**: Collaborate with teammates in the case timeline by tagging users and adding notes.
43+
- **Send notifications**: Alert stakeholders with Slack, Microsoft Teams, email, or webhooks.
44+
- **Escalate issues**: Trigger an incident or page an on-call responder using [Incident Management][1], [On-Call][2], [Workflow Automation][3], or third-party tools.
45+
- **Sync with external tools**: Keep Jira and ServiceNow records in sync to ensure external stakeholders stay up to date.
46+
47+
{{< img src="/service_management/events/triage_inbox/event_mgmt_inbox_right_hand_panel.png" alt="Event Management Inbox right hand panel, highlighting Escalate drop down" style="width:100%;" >}}
48+
49+
## Take Action
50+
51+
- **Mark root cause**: Identify and mark a related event, such as a faulty change, as the root cause.
52+
- **Run workflows**: Execute remediation runbooks manually or trigger them conditionally with [Case Automation Rules][5].
53+
- **Merge cases**: Combine related cases to streamline investigations.
54+
- **Split cases**: Separate alerts that require individual investigation.
55+
56+
**Note**: When all alerts in a case are resolved, the system automatically closes the case. You can also manually mark a case as resolved.
57+
58+
## Further Reading
59+
60+
{{< partial name="whats-next/whats-next.html" >}}
61+
62+
[1]: /service_management/incident_management/
63+
[2]: /service_management/on-call/
64+
[3]: /actions/workflows/
65+
[4]: https://app.datadoghq.com/event/correlation
66+
[5]: /service_management/case_management/automation_rules/
Binary file not shown.
397 KB
Loading

0 commit comments

Comments
 (0)