---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/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


---

# Manually create an SRM alert

# Manually create an SRM alert {#ariaid-title1}

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

Create an alert for testing purposes or if you think an issue poses a risk.

## Before you begin

Role required: srm_admin, srm_manager, or srm_responder

## Procedure

1. Navigate to WorkspacesService Operations Workspace.  
   You're taken to your SRM Home page.  
   Note:  
   If you use other Service Operations Workspace (SOW) applications, you may see the SOW Home page instead of the SRM Home page. The SOW Home page includes SRM alerts and incidents in its metrics.
2. In the navigation pane, select Services.
3. Select the service that you want to trigger an alert for.
4. Select the Related alerts tab.
5. Select Trigger alert and fill out the Trigger an alert form.  
   To trigger an alert, you must first create an event to get processed. Only Service is required.  
   {#sr-create-alert__table_ows_1c4_b2c__entry__2}

   | Field | Description |
   |-|-|
   | Service | Select a service for the event. |
   | Source | Manual. |
   | Node | Enter the name of the node (for example, FQDN, IP address, or MAC address) associated with the event. |
   | Type | Enter a type of event. |
   | Resource | Enter a node resource (process or service) associated with the event. |
   | Metric Name | Enter the name of the metric associated with the event. |
   | Source instance | Enter a data source for the event. |
   | Message key | Enter an identifier for multiple events related to the same event. |
   | Severity | Select the expected impact of this event. Choices are: * Critical: Immediate action is required. The resource is either not functional or critical problems are imminent. * Major: Major functionality is severely impaired or performance has degraded. * Minor (default): Partial, non-critical loss of functionality or performance degradation occurred. * Warning: Attention is required, even though the resource is still functional. * OK: The resource is still functional. {#sr-create-alert__ul_q3l_4bb_hzb} |
   | Time of the event | Select the date and time that the event occurred in the source system. |
   | Description | Enter information describing the event. |
   | Additional information | Add more information relevant to the event. |
   | Processing notes | Enter relevant processing information. |
   [Table 1. Trigger an alert]

   {#sr-create-alert__table_ows_1c4_b2c}
6. Select Trigger.  
   Service Reliability Management (SRM) creates an event to generate the alert. Refresh the screen to see the event processing results.

   Express List automatically displays your alert. If enabled, SRM triggers the applicable automations and on-call escalation workflows.

## What to do next

Consider making the following optional adjustments to your alert for testing purposes or team collaboration:

* Acknowledge the alert or assign it to someone on your team.
* Add comments or work notes in the Compose panel.
* Add an attachment related to the alert using the attachment icon ![Attachment icon]().
{#sr-create-alert__ul_u2p_sc4_b2c}

*[\>]: and then