> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/data-security-documentation/data-management/broker-vm/broker-vm-notifications.md).
# Broker VM notifications
Learn about the notifications that are relevant to Cortex Data Security Broker VMs.
To help you monitor your Broker VM version, connectivity, and high availability clusters, Cortex Data Security sends notifications to your Cortex Data Security console Notification Center.
Cortex Data Security sends the following notifications:
Add Cluster
Notifies when a cluster was added.
Applet Activated
Notifies when an applet is activated on a cluster.
Applet configuration
Notifies when an applet on a cluster configuration was updated.
Applet Deactivated
Notifies when an applet is deactivates on a cluster.
Broker VM Connectivity
Notifies when the Broker VM has lost connectivity to Cortex Cloud .
Broker VM Disk Usage
Notifies when the Broker VM is utilizing over 90% of the allocated disk space.
Cluster Configuration
* Notifies when a Broker VM node was added to a cluster.
* Notifies when a Broker VM node was removed from a cluster.
* Notifies when the configuration for the cluster needs to be set.
Cluster failover
* Notifies when a failover is initiated in the cluster from one Broker VM node to another.
* Notifies when a failover completed successfully. The Broker VM is now Primary in the cluster.
* Notifies when a failover in the cluster completed with errors and error message.
* Notifies when couldn't perform a failover in the cluster as there is no available standby node with sufficient redundancy.
Cluster health declined
* Notifies when failed to detect an available standby Broker VM node in the cluster.
* Notifies when critical errors detected in the cluster and there is no available standby Broker VM node for failover.
Cluster health recovered
Notifies when detected an available standby Broker VM node in the cluster.
Disk space allocation on broker
Notifies whether the disk space allocated for data caching in the Broker VM has been increased successfully. If not, the notification includes the errors encountered during the process. For more information on allocating disk space to the Broker VM, see [Increase Broker VM storage allocated for data caching](/cortex-cloud-posture-management/data-management/broker-vm/manage-broker-vm/increase-broker-vm-storage-allocated-for-data-caching.md).
Broker VM requires a reboot
Notifies after a Broker VM update whether a broker needs a reboot to finish installing important updates.
New Broker VM Version
Notifies when a new Broker VM version has been released.
* If the Broker VM Auto Upgrade is disabled, the notification includes a link to the latest release information. It is recommend you upgrade to the latest version.
* If the Broker VM Auto Upgrade is enabled, 12 hours after the release you are notified of the latest upgrade, or you are notified that the upgrade failed. In such a case, open a Palo Alto Networks Support Ticket.
Reinstall Broker VM with a new image
For all brokers that were deployed with an old Broker VM image, downloaded prior to July 9th, 2023 (installed with Ubuntu 18.04 or earlier), the Broker VM must be reinstalled with a new image (installed with Ubuntu 20.04 or later) before upgrading to the latest version. The name of the Broker VM to upgrade is indicated with a link to the instructions.
{% hint style="info" %}
#### Note
For more information on upgrading to a new Broker VM image, see [Migrating to a New Broker VM Image](/cortex-cloud-posture-management/migrate-to-a-new-broker-vm-image/migrating-to-a-new-broker-vm-image.md).
{% endhint %}
Remove Cluster
Notifies when a cluster was removed.
To ensure you stay informed about Broker VM activity, you can also configure notification forwarding to forward your Broker audit logs to an email distribution list or Syslog server. For more information about the Broker VM audit logs, see Monitor Broker VM Activity.
---
# 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://cortex-docs.paloaltonetworks.com/data-security-documentation/data-management/broker-vm/broker-vm-notifications.md?ask=&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.