Stream Connect Alerting properties

  • Release version: Zurich
  • Updated July 31, 2025
  • 6 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Stream Connect Alerting properties

    Stream Connect Alerting properties in ServiceNow enable customers to monitor and manage alerts related to message streaming and replication within the Integration Hub. These alerts help ensure reliable data flow by notifying users of issues such as producer failures, consumer problems, queue processing delays, and topic replication statuses.

    Show full answer Show less

    Access to Stream Connect Alerting properties requires the Kafka Admin role and is located under Integration Hub > Stream Connect > Alert Properties.

    Key Alerts and Their Purpose

    • Producer Failed Alert: Triggered when a message producer fails to send messages to a topic.
    • Queue Depth Processing Time Alert: Triggered when the estimated time to process queued messages exceeds defined thresholds.
    • Consumer Poll Failed Alert: Triggered when a consumer cannot connect to or read messages from a topic, such as when a topic is deleted but subscriptions remain active.
    • Consumer Processing Alert: Triggered when a consumer fails to process messages from a topic.
    • Topic Replication Failed Age Alert: Triggered when topic replication status remains FAILED beyond a set duration.
    • Topic Replication Inactivity Alert: Triggered when there is no message replication activity between source and destination topics for a specified time.

    Configurable Alert Properties

    For each alert type, customers can configure:

    • Severity Level: Defines the alert importance with options such as IGNORED, INFO, WARNING, and CRITICAL (default varies per alert).
    • Detection Interval: The minimum time in seconds between consecutive detections to treat them as separate events and alerts (default generally 3600 seconds).
    • Notification Scope: Choice between receiving a single global notification or individual notifications per topic, consumer, or replication instance, depending on alert type.
    • Thresholds: For alerts related to timing (e.g., queue processing time, replication inactivity), thresholds are set for INFO, WARNING, and CRITICAL severities to define when alerts trigger.
    • Disabling Alerts: Setting all severity thresholds to 0 disables the alert entirely.

    Practical Benefits for ServiceNow Customers

    By configuring these alert properties, customers can proactively monitor streaming infrastructure health, detect and respond to issues quickly, and tailor alerting granularity to their operational needs. This leads to improved data flow reliability and faster troubleshooting of streaming and replication problems.

    Specify alert properties and how alerts are managed in Stream Connect.

    Alerts

    To view Stream Connect Alerting properties, navigate to Integration Hub > Stream Connect > Alert Properties. You must have the Kafka Admin role to view or modify alerting properties.

    The Stream Connect Alerting UI has the following alerts.
    • 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.
    Table 1. Producer Failed Alert
    Alert level

    Severity level for the alert.

    The options are:
    • IGNORED
    • INFO
    • WARNING
    • CRITICAL

    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
    Table 2. Queue Depth Processing Time Alert
    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
    Table 3. Consumer Poll Failed Alert
    Alert level

    Severity level for the alert.

    The options are:
    • IGNORED
    • INFO
    • WARNING
    • CRITICAL

    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
    Table 4. Consumer Processing Alert
    Alert level

    Severity level for the alert.

    The options are:
    • IGNORED
    • INFO
    • WARNING
    • CRITICAL

    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
    Table 5. Topic Replication Failed Age Alert
    Threshold, in seconds, for the topic replication failed age estimate to be considered info.

    Triggered when the topic replication status remains FAILED for longer than the specified value. With a MID Server cluster, this alert is triggered if any of the MID Servers in the cluster has a topic replication status that remains FAILED for longer than the specified value.

    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
    Table 6. Topic Replication Inactivity Alert
    Threshold, in seconds, for the topic replication inactivity estimate to be considered info.

    If there are no messages replicated between the source and destination topic by any server 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