---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Notifications for breached error budgets

# Notifications for breached error budgets {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 3, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Details about the notifications that teams receive for breached error budget policies.

## When notifications are sent {#srm-notifications-messages__section_nzk_ljg_wfc}

When a service or configuration item breaches its error budget policy and a notification destination is set, Service Reliability Management (SRM) sends a notification to the configured Microsoft Teams channel.

## Notification content {#srm-notifications-messages__section_eml_wkg_wfc}

The message contains details about the breach to help team members learn about the issue and act. In Microsoft Teams, the message is titled `Error budget policy violation` and lists the following information:

* Service level objective - Name of the service level objective (SLO), for example, `Navigation service availability 99.95`.
* Service/CI - Name of the associated service or configuration time. Select the name to open the relevant service in SRM.
* Policy name - Name of the error budget policy that was breached.
* Reliability - The service state: critical, at risk, or stable.
* Error budget remaining - Percentage of error budget left at the time of the breach.
* View SLO in ServiceNow - Link to view the SLO details in SRM.
{#srm-notifications-messages__ul_jtk_s3h_wfc}

## Sample notification {#srm-notifications-messages__section_qwq_yfd_1gc}

The following image is a sample notification in Microsoft Teams. It shows an error budget policy violation for the Retail service and details about the SLO, service state, and error budget remaining.

## Related documentation {#srm-notifications-messages__section_iwz_14h_wfc}

See [Create a notification destination in SRM](https://www.servicenow.com/docs/oB0UCf2MDByXTzLBWyomUw "Set up notification destinations to help keep teams informed about service reliability.") and [Create SLOs, SLIs, and error budget policies](https://www.servicenow.com/docs/PAyr1az_9UN3VPV1pJtwxA "Define service level objectives (SLOs), service level indicators (SLIs), and error budget policies to monitor service health. These tools help you and your teams track performance and take action when needed.").