--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management Release : - australia ft:locale : - de-DE ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Working with alerts in SRM # Working with alerts in SRM {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer Events take the form of alerts under reliability tasks in SRM. From creation to resolution, SRM enables you to manage your alerts through the entire alert life cycle. Alerts are created manually or within SRM using different integrations. If the Alert automation application has been installed, alerts can be grouped during ingestion and before Alert management automations are run. The Assigned to field on an alert specifies who should be notified. When a team is selected as a responder, team rules are checked to determine which schedule to use for the notifications. An alert can be assigned to multiple teams. The Assigned to field is cleared when the Assigned-team or Service field is updated on an alert. Escalation policies run on newly assigned teams. The field remains cleared until a user on the new team acknowledges an escalation notification. Hinweis: If the Service is changed and the new Service does not have an assigned team, no changes occur. When a service is deleted, its integrations, alerts, incidents, and automations are removed. Deleting a service isn't a recoverable action so consider deactivating the service instead. Responders and above are notified for updates to alerts based on their notification preferences. Selecting the attachments ![Attachments icon.]() icon toggles the Attachments panel open or closed. For more information on the areas and fields available in an alert, see [SRM alert workspace](https://servicenow-prod.fluidtopics.net/7qc6ONvHZIBnHy5HahCE9A "The alert workspace contains various areas containing alert details and possible actions."). Respond to an alert in the following ways: * [Acknowledge an SRM alert](https://servicenow-prod.fluidtopics.net/X1QFTAP_1VSvyIVxVV_8gg "Place an alert in the Acknowledged state if the alert has issues that must be addressed. You can acknowledge an alert without assigning it to yourself.") that requires attention. * [Add work notes to an SRM alert](https://servicenow-prod.fluidtopics.net/one7roQ4YH1~IzS8Q_c3Kg "Add work notes to an alert that are visible to all members of the alert team.") * [Update the severity of one or more SRM alerts](https://servicenow-prod.fluidtopics.net/snt8YvUCe8MUFRmilNPdkg "If the severity of an alert should be changed, you can manually update it to reflect its new criticality.") * [Reassign an SRM alert](https://servicenow-prod.fluidtopics.net/bU4xyGDEd6ApwrjOOsll5Q "Reassign an alert to a responder when the alert task should be addressed by a particular user.") * [Manually create SRM tags](https://servicenow-prod.fluidtopics.net/tpwOycR6TEIvtGMp6omgww "Add tags to classify, categorize, and add context to data. Service Reliability Management (SRM) imports tags and attaches them to services, alerts, and incidents. You can also manually create tags.") * [Close an SRM alert](https://servicenow-prod.fluidtopics.net/JRsmSufwt1bvwPIAr8PbSQ "Close an alert, if you think it is not an issue, or if it has already been handled.") If there have been no updates, open alerts are automatically closed after 7 days. Closed alerts are automatically deleted after 90 days. * [Reopen an SRM alert](https://servicenow-prod.fluidtopics.net/O4ts2mdbSL1~L9cfbSRwYA "Reopen a closed alert if you think the issue is not yet resolved.") {#sr-work-alerts__ul_u52_rlr_tnb} * **[Acknowledge an SRM alert](https://servicenow-prod.fluidtopics.net/X1QFTAP_1VSvyIVxVV_8gg)** Place an alert in the Acknowledged state if the alert has issues that must be addressed. You can acknowledge an alert without assigning it to yourself. * **[Update the severity of one or more SRM alerts](https://servicenow-prod.fluidtopics.net/snt8YvUCe8MUFRmilNPdkg)** If the severity of an alert should be changed, you can manually update it to reflect its new criticality. * **[Update the state of one or more SRM alerts](https://servicenow-prod.fluidtopics.net/Xo6F7i7FVfE_nLD5yETVOw)** If the state of an alert must be changed, you can manually update it to reflect its new status. * **[Add or edit a task on an SRM alert](https://servicenow-prod.fluidtopics.net/XIxxNaNBtKy8QRD3v_MY7w)** If an alert has a task, you can manually add it. * **[Add or edit a parent on an SRM alert](https://servicenow-prod.fluidtopics.net/KvAwDKvysfGJca2JuDM2uA)** If an alert has a parent, you can manually update it to reflect its new criteria. * **[Add or edit a knowledge article to an SRM alert](https://servicenow-prod.fluidtopics.net/jInTzjTwdHGZ_nOQ5TEi2Q)** If an alert has a knowledge article associated with it, you can manually add it. * **[Reassign an SRM alert](https://servicenow-prod.fluidtopics.net/bU4xyGDEd6ApwrjOOsll5Q)** Reassign an alert to a responder when the alert task should be addressed by a particular user. * **[Add work notes to an SRM alert](https://servicenow-prod.fluidtopics.net/one7roQ4YH1~IzS8Q_c3Kg)** Add work notes to an alert that are visible to all members of the alert team. * **[Close an SRM alert](https://servicenow-prod.fluidtopics.net/JRsmSufwt1bvwPIAr8PbSQ)** Close an alert, if you think it is not an issue, or if it has already been handled. * **[Reopen an SRM alert](https://servicenow-prod.fluidtopics.net/O4ts2mdbSL1~L9cfbSRwYA)** Reopen a closed alert if you think the issue is not yet resolved. * **[Promote an SRM alert to an incident](https://servicenow-prod.fluidtopics.net/mdH84ZhxSGS_WnFrrRv_3w)** Promote an alert to an incident if you think the alert poses a serious issue and must be taken care of as soon as possible.