Stream Connect Alerting properties
Summarize
Summary of Stream Connect Alerting properties
Stream Connect Alerting properties in ServiceNow allow you to specify and manage alerts related to Kafka stream integrations. These properties help monitor the health and performance of producers, consumers, and topic replications within Stream Connect. Access to configure these alert properties requires the Kafka Admin role.
Show less
Key Alerts and Their Purpose
- Producer Failed Alert: Triggered when a producer fails to send messages to a topic.
- Queue Depth Processing Time Alert: Triggered when message processing time exceeds defined thresholds.
- Consumer Poll Failed Alert: Triggered when a consumer cannot connect to or read from a topic.
- Consumer Processing Alert: Triggered when a consumer fails to process messages.
- Topic Replication Failed Age Alert: Triggered when topic replication remains in a failed state longer than configured.
- Topic Replication Inactivity Alert: Triggered when topic replication is inactive beyond a specified duration.
Configurable Alert Properties
For each alert type, you can configure:
- Severity Level: Set the alert level to IGNORED, INFO, WARNING, or CRITICAL depending on the importance.
- Time Interval Between Notifications: Define the minimum seconds between two detections so multiple occurrences within that timeframe count as one alert, reducing notification noise.
- Notification Scope: Choose whether to receive alerts globally for all topics/consumers or individually per topic, consumer, or topic replication, enabling granular alert management.
- Threshold Values: For alerts like Queue Depth Processing Time, Topic Replication Failed Age, and Topic Replication Inactivity, you can set seconds thresholds for INFO, WARNING, and CRITICAL levels. Setting thresholds to 0 disables alerts at that level.
Practical Benefits for ServiceNow Customers
By configuring Stream Connect alerting properties, you gain proactive monitoring of your Kafka integrations, enabling timely detection and resolution of issues such as message production failures, consumer connectivity problems, and replication delays or inactivity. Tailoring severity levels and notification scopes helps reduce alert fatigue and focus on critical events, optimizing your integration reliability and operational efficiency.
Specify alert properties and how alerts are managed in Stream Connect.
Alerts
To view Stream Connect Alerting properties, navigate to . You must have the Kafka Admin role to view or modify alerting properties.
- Producer Failed Alert. Triggered when a producer fails to produce messages to a topic.
- Queue Depth Processing Time Alert. Triggered when the estimated message processing time exceeds the specified value.
- Consumer Poll Failed Alert. Triggered when a consumer is unable to connect to a topic or read the messages in a topic. For example, if a topic is deleted from Hermes while the associated subscription is still active.
- Consumer Processing Alert. Triggered when a consumer fails to process messages from a topic.
- Topic Replication Failed Age Alert. Triggered when the topic replication status remains FAILED for longer than the specified value.
- Topic Replication Inactivity Alert. Triggered when topic replication is inactive for longer than the specified value.
| Alert level |
Severity level for the alert. The options are:
Default: CRITICAL |
| Time interval, in seconds, required between two detections to have them count as separate events. |
The minimum number of seconds to wait before sending another notification for the same alert. Detections within this time interval count as a single alert and are linked to the same alert record. Default: 3600 seconds |
| Specifies the number of separate notifications to send when there's a Producer Failed Alert for multiple topics. Select Global to receive a single notification, or Per Topic to receive a notification for each topic. |
Select Per Topic to create an alert for each topic, or Global to create one alert for all topics. Default: Global |
| Threshold, in seconds, for the queue depth processing time estimate to be considered info. |
If the estimated queue processing time is greater than this value, generate an alert with a severity of INFO. Default: 0 seconds A value of 0 disables the alert at the specified severity level. To completely disable the alert, set the value to 0 for all three severity levels (INFO, WARNING, and CRITICAL). |
| Threshold, in seconds, for the queue depth processing time estimate to be considered a warning. |
If the estimated queue processing time is greater than this value, generate an alert with a severity of WARNING. Default: 14400 seconds |
| Threshold, in seconds, for the queue depth processing time estimate to be considered critical. |
If the estimated queue processing time is greater than this value, generate an alert with a severity of CRITICAL. Default: 86400 seconds |
| Time interval, in seconds, required between two detections to have them count as separate events. |
The minimum number of seconds to wait before sending another notification for the same alert. Detections within this time interval count as a single alert and are linked to the same alert record. Default: 3600 seconds |
| Specifies the number of separate notifications to send when there's a Queue Depth Alert for multiple consumers. Select Global to receive a single notification, or Per Consumer to receive a notification for each consumer. |
Select Per Consumer to create an alert for each consumer, or Global to create one alert for all consumers. Default: Global |
| Alert level |
Severity level for the alert. The options are:
Default: CRITICAL |
| Time interval, in seconds, required between two detections to have them count as separate events. |
The minimum number of seconds to wait before sending another notification for the same alert. Detections within this time interval count as a single alert and are linked to the same alert record. Default: 3600 seconds |
| Specifies the number of separate notifications to send when there's a Consumer Poll Failed Alert for multiple consumers. Select Global to receive a single notification, or Per Consumer to receive a notification for each consumer. |
Select Per Consumer to create an alert for each consumer, or Global to create one alert for all consumers. Default: Global |
| Alert level |
Severity level for the alert. The options are:
Default: WARNING |
| Time interval, in seconds, required between two detections to have them count as separate events. |
The minimum number of seconds to wait before sending another notification for the same alert. Detections within this time interval count as a single alert and are linked to the same alert record. Default: 3600 seconds |
| Specifies the number of separate notifications to send when there's a Consumer Processing Alert for multiple consumers. Select Global to receive a single notification, or Per Consumer to receive a notification for each consumer. |
Select Per Consumer to create an alert for each consumer, or Global to create one alert for all consumers. Default: Per Consumer |
| Threshold, in seconds, for the topic replication failed age estimate to be considered info. |
If the topic replication status remains FAILED for longer than this value, generate an alert with a severity of INFO. Default: 0 seconds A value of 0 disables the alert at the specified severity level. To completely disable the alert, set the value to 0 for all three severity levels (INFO, WARNING, and CRITICAL). |
| Threshold, in seconds, for the topic replication failed age estimate to be considered a warning. |
If the topic replication status remains FAILED for longer than this value, generate an alert with a severity of WARNING. Default: 1800 seconds |
| Threshold, in seconds, for the topic replication failed age estimate to be considered critical. |
If the topic replication status remains FAILED for longer than this value, generate an alert with a severity of CRITICAL. Default: 3600 seconds |
| Time interval, in seconds, required between two detections to have them count as separate events. |
The minimum number of seconds to wait before sending another notification for the same alert. Detections within this time interval count as a single alert and are linked to the same alert record. Default: 3600 seconds |
| Specifies the number of separate notifications to send when there's a Topic Replication Failed Alert for multiple topic replications. Select Global to receive a single notification, or Per Topic Replication to receive a notification for each topic replication. |
Select Per Topic Replication to create an alert for each topic replication, or Global to create one alert for all topic replications. Default: Global |
| Threshold, in seconds, for the topic replication inactivity estimate to be considered info. | If topic replication is inactive for longer than this value, generate an alert with a severity of INFO. Default: 14400 seconds |
| Threshold, in seconds, for the topic replication inactivity estimate to be considered a warning. |
If topic replication is inactive for longer than this value, generate an alert with a severity of WARNING. |
| Threshold, in seconds, for the topic replication inactivity estimate to be considered critical. |
If topic replication is inactive for longer than this value, generate an alert with a severity of CRITICAL. |
| Time interval, in seconds, required between two detections to have them count as separate events. |
The minimum number of seconds to wait before sending another notification for the same alert. Detections within this time interval count as a single alert and are linked to the same alert record. Default: 3600 seconds |
| Specifies the number of separate notifications to send when there's a Topic Replication Inactivity Alert for multiple replications. Select Global to receive a single notification, or Per Topic Replication to receive a notification for each topic replication. |
Select Per Topic Replication to create an alert for each topic replication, or Global to create one alert for all topic replications. Default: Per Topic Replication |