# Control Center Alerts for Confluent Platform Control Center enables you to detect anomalous events in the monitoring data and configure alerts to occur when those events are detected. For example, you can detect when a cluster goes down and configure an email to be sent. Considerations: : - When RBAC is enabled in Control Center, there are some nuances to trigger, action, and alert access. For details, see [About alerts access](../security/c3-rbac.md#c3-rbac-alerts-access). - Alerts are not supported for [Reduced infrastructure mode](../overview.md#reduced-infra-mode). - For access to the **Alerts** page, see: [Manage Control Center Alerts and History for Confluent Platform](navigate.md#c3-alerts-navigation) ## Triggers and actions An alert consists of a trigger and one or more actions. Each trigger is based on a metric with condition value criteria that determines when the trigger should fire. For more about Triggers, see [Manage Control Center Alert Triggers for Confluent Platform](triggers.md#trigger-mgmnt). Any actions associated with the trigger are executed when the criteria is met. Supported actions for a trigger include: - Sending an email notification to one or more accounts - Sending a Slack webhook notification - Sending a PagerDuty webhook notification that creates an incident ticket A trigger can be associated with any number of defined actions. For more about actions, see [Manage Control Center Alert Actions for Confluent Platform](actions.md#actions-mgmnt). To learn how to configure some example triggers and actions, see [Control Center Alerts Usage Example for Confluent Platform](examples.md#examples-c3-alert-actions-triggers). When a trigger fires, it executes all its associated enabled actions for which the `Max send rate` has not been exceeded. If the `Max send rate` of a particular action has been exceeded, the trigger event is added to a queue associated with the action and is included in the action event the next time it is executed (actions can report a set of triggers, not just one trigger). #### NOTE Queuing does not occur when alerts (actions) are [paused](actions.md#pause-resume-alerts-actions-ui) because triggers are ignored during that interim. The maximum triggered events per alert (default: 1000) is controlled by the `confluent.controlcenter.max.trigger.events.per.alert.config` option. Detection of anomalous events (*triggering* criteria) is decoupled from the alert *actions* that are taken when a triggering event occurs. This means that triggers and actions are defined independently, which provides flexibility when setting one or more actions to perform when a trigger fires. ## Additional resources - [Troubleshoot Control Center Alerts for Confluent Platform](trouble.md#troubleshoot-alerts) - [Configure PagerDuty Control Center Alerts for Confluent Platform](pagerduty.md#c3-alerts-pagerduty-email-integration) - [Control Center Alerts REST API for Confluent Platform](rest.md#integration-alerts)