Skip to content

Service health updates for ga #28326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dd-mergequeue merged 2 commits into from
Mar 25, 2025
Merged

Service health updates for ga #28326

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3fd4917
Service health updates for ga
lee-brian Mar 24, 2025
aad6490
resetting go files
lee-brian Mar 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 8 additions & 12 deletions content/en/tracing/services/service_page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Selecting a service on the Software Catalog leads you to the detailed service pa

Consult on this page:

* [Service health](#service-health) (in Preview)
* [Service health](#service-health)
* [Service monitor states](#service-monitor)
* [Watchdog Insights](#watchdog-insights)
* [Summary cards](#summary-cards)
Expand All @@ -47,30 +47,26 @@ Consult on this page:

## Service health

{{< callout header="Opt in to the Preview!" url="https://www.datadoghq.com/product-preview/service-health/" >}}
Service health is in Preview. To request access, complete the form.
{{< /callout >}}
**Service health** provides a real-time summary of service status to help you identify services that need immediate attention.

**Service Health** provides a real-time summary of signals to help you understand if a service needs your attention.

Service health considers multiple signals (including monitors, incidents, Watchdog insights, and error tracking issues), and surfaces the most critical alerts as a badge on Software Catalog and service pages.
Service health integrates multiple signals (monitors, incidents, and Watchdog Insights) into a single alert. See which services are in a critical state to detect and troubleshoot issues faster.

{{< img src="/tracing/services/service_page/service-health3.png" alt="Service health on the service page and service dependency map." style="width:100%;" >}}

Service health is available in several places in Datadog:

1. [Software Catalog][23]
2. Service pages
3. Service dependendency maps
3. Service dependendency maps, if Watchdog detects that an issue spans multiple service dependencies.
4. Service pills

The Service Health banner displays the status of your service as *Warning*, or *Alert* if at least one of the following conditions is met:
Service health displays the status of your service as *Critical* or *Warning* if at least one of the following conditions is met:

| Status | Condition |
|-------------|------------------------------------------------------------|
| **Alert** | **Monitors**: <br>- A non-muted monitor with a paging integration setup (PagerDuty or Opsgenie) is triggered.<br><br>**Incidents**: <br>- An incident of any severity is active.<br><br>**Watchdog Insights**: <br>- A faulty deployment is active.<br>- An ongoing APM latency/error rate alert is active. |
| **Warning** | **Monitors**: <br>- A non-muted warning monitor with a paging integration setup (PagerDuty or Opsgenie) is triggered.<br><br>**Incidents**: <br>- An incident of any severity is in a stable state.<br><br>**Watchdog Insights**: <br>- An ongoing log anomaly alert is active.<br><br>**Error Tracking Issues**: <br>- A new issue (within 48 hours) requires review. | |
| **No Alerts** | No signal from critical or alert state is active. | ||
| **Critical** | **Monitors**: <br>- A non-muted monitor with a paging integration setup (PagerDuty or Opsgenie) is in an `ALERT` state and triggered within the `past 2 days`.<br><br>**Incidents**: <br>- An incident of any severity is active.<br><br>**Watchdog Insights**: <br>- A faulty deployment is ongoing.<br>- An APM latency/error rate alert is ongoing. |
| **Warning** | **Monitors**: <br>- A non-muted warning monitor with a paging integration setup (PagerDuty or Opsgenie) is in a `WARN` state and triggered within the `past 2 days`.<br><br>**Incidents**: <br>- An incident of any severity is stable .<br><br>**Watchdog Insights**: <br>- A log anomaly alert is ongoing. | |
| **Ok** | No alerts from the critical or warning state are active. | ||

## Service monitor

Expand Down
Loading