Notification categories and event mapping
Cloudera Data Engineering events are organized into four primary notification categories across the Cloudera Data Engineering Service and Virtual Clusters. Subscribers can filter incoming alerts within each category by severity to ensure they receive only the operational notifications relevant to their role.
Severity levels
When configuring subscriptions, you can filter delivery based on the following severity thresholds:
- Info: Triggered during routine operational events and successful state transitions (for example, Service Ready, VC Created, Upgrade Completed, Resource Pool Modified, State Config Sync Succeeded).
- Warning: Triggered when administrative action is required to prevent upcoming operational disruption (for example, Stale Configs Detected, TLS certificate expiration approaching within 30 days).
- Error: Triggered when a critical failure occurs that prevents a service or virtual cluster from operating normally (example, Service Provisioning Failed, VC Creation Failed, Upgrade Failed, TLS Certificate Expired, State Config Sync Failed).
Notification categories
The following table provides the available Cloudera Data Engineering notification categories, mapping each to its resource scope, supported severity filters, triggered events, and default retention period:
| Notification category | Resource scope | Supported severities | Description | Triggered events | Default Time to Live (TTL) |
|---|---|---|---|---|---|
| Data Engineering Service - Configuration updates | Service | Info, Warning, and Error |
Tracks Cloudera Data Engineering Service configuration and cluster health events |
|
3 days |
| Data Engineering Service - Lifecycle updates | Service | Info and Error |
Tracks overall Cloudera Data Engineering Service lifecycle events. |
|
3 days |
| Data Engineering Virtual Cluster - Configuration updates | Virtual Cluster | Info, Warning, and Error |
Tracks Virtual Cluster configuration changes. |
|
3 days |
| Data Engineering Virtual Cluster - Lifecycle updates | Virtual Cluster | INFO and ERROR |
Tracks Virtual Cluster lifecycle changes. |
|
3 days |
