> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/alerts/alert-notifications-state-changes.md).

# Alert Notifications on State Change

Learn whether you can enable alert notifications to an external integration when an alert status is updated.

The following table provides an overview of how Prisma Cloud sends alerts for all states. By default, alert notifications are sent for the **Open** state only.

| Integrations            | Alert Status |         |          |     |
| ----------------------- | ------------ | ------- | -------- | --- |
| Open                    | Dismissed    | Snoozed | Resolved |     |
| Amazon SQS              | Yes          | Yes     | Yes      | Yes |
| Amazon S3               | Yes          | Yes     | Yes      | Yes |
| Email                   | Yes          | Yes     | Yes      | Yes |
| ServiceNow              | Yes          | Yes     | Yes      | Yes |
| Slack                   | Yes          | Yes     | Yes      | Yes |
| Splunk                  | Yes          | Yes     | Yes      | Yes |
| Cortex XSOAR            | Yes          | No      | No       | No  |
| Jira                    | Yes          | No      | No       | Yes |
| Microsoft Teams         | Yes          | Yes     | Yes      | Yes |
| AWS Security Hub        | Yes          | Yes     | Yes      | Yes |
| Google Cloud SCC        | Yes          | Yes     | Yes      | Yes |
| PagerDuty               | Yes          | Yes     | Yes      | Yes |
| Azure Service Bus Queue | Yes          | Yes     | Yes      | Yes |
| Webhooks                | Yes          | Yes     | Yes      | Yes |

Alert notifications are sent for **Resolved** issues when you perform the following actions:

* Policy is disabled—Yes
* Policy is deleted—Yes
* Alert rule is disabled—Yes
* Alert rule is updated and the policy that triggered the alert is removed—Yes
* Alert rule is deleted—No
* Resource is updated and the policy violation is addressed when the next scan occurs—Yes
* Resource is deleted and the next scan discovers that this is no longer an issue—Yes

In some cases, when you perform two actions in quick succession and a race condition occurs you may not receive notifications for the state change. For example:

* When an alert is associated with multiple alert rules, and the alert rules are disabled sequentially, you may not receive resolve notification on all the alert rules. It will be sent out to the last alert rule against which the alert was resolved.
* When you update an alert rule to remove a policy and also disable or delete the policy, you may not receive the resolve notification.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.prismacloud.io/content-collections/alerts/alert-notifications-state-changes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
