Alerts

User can configure following alerts types:

  • No Active Dataplane Instances: Allows users to add alerts when there are no active dataplane instances running, which could indicate service disruption or deployment issues.

  • Source Data Ingestion Spike: Allows users to add alerts when source data ingestion volume suddenly increases beyond normal thresholds, which could indicate data quality issues or system stress.

  • Source No Data: Allows users to add alerts when source is not emitting or pushing any data.

  • Destination Errors: Allows users to add alerts when some error is occurring either configuring the destination or accessing it.

  • Site Service Pod Restart: Allows users to add alerts when site service pods are restarting frequently, which could indicate underlying infrastructure problems or resource constraints.

  • Dataplane High Memory Usage: Allows users to add alerts when memory usage crosses a certain threshold.

  • Destination No Data: Allows users to add alerts when no data is being pushed to the destination

  • Source Errors: Allows users to add alerts when some error is occurring either configuring the source, accessing the source or processing its data.

  • Destination Data Ingestion Drop: Allows users to add alerts when destination data ingestion drops when compared to historical data.

  • Source Data Ingestion Drop: Allows users to add alerts when source data ingestion drops when compared to historical data.

  • Dataplane High CPU Usage: Allows users to add alerts when cpu usage crosses a certain threshold.

  • Site Down: Allows users to add alerts when the site goes down.

  • Pipeline Optimization Drop: Allows users to add alerts when pipeline performance optimization metrics decline, indicating reduced efficiency in data processing or potential bottlenecks in the pipeline.

Adding Alerts

To create a new alert rule:

  1. Navigate to the Alerts section in the side panel

  2. Select the Manage Alerts tab (if not already selected)

  3. Click the Create Alert button

After clicking Create Alert, you'll be presented with a Create Alert form where you can configure the alert rule, set conditions, define severity levels, and assign notification channels.

Note: Alert rules define the monitoring conditions and thresholds that trigger notifications. Once created, alerts will actively monitor your system and send notifications through your assigned channels when the specified conditions are met.

Select an alert rule in the Alert Type select box options.

Configuring Alert

Once an alert rule is selected, configure the following details to customize your alert:

  • Alert Type: The specific alert condition selected as a prerequisite such as Source No Data or Dataplane High Memory Usage.

  • Name: A descriptive, user-defined name that uniquely identifies this alert rule for easy management and recognition.

  • Description (Optional): Additional context about the alert's purpose, expected conditions, or response actions to help team members understand its significance.

  • Alert Severity: Define the urgency level of the alert to prioritize response efforts:

    Options
    Description

    Low

    Informational alerts requiring minimal attention

    Medium

    Moderate issues that should be addressed during business hours

    High

    Urgent issues requiring prompt attention

    Critical

    Severe problems demanding immediate response

  • Labels (Optional): Custom key-value pairs that provide additional metadata and context in alert notifications, useful for filtering, routing, or automated processing.

  • Time Window (Optional): The evaluation period in seconds during which the alert condition must persist before triggering. This prevents false alarms from temporary spikes or brief outages. Default: 120 seconds.

Assigning Channels

Once an alert rule is configured, click Next to assign it to one or more notification channels for delivering alerts through your preferred communication methods.

You can choose to:

  • Create new channels - Set up fresh notification channels with custom configurations

  • Use existing channels - Select from previously configured notification channels

After selecting your desired channels, click Save to create and activate the alert rule in the system. The alert will now monitor for the specified conditions and send notifications through your chosen channels when triggered.

Create New Channels

Set up fresh notification channels with custom configurations.

Channel Configuration Fields:

  • Name: User-defined name for the channel that serves as a unique identifier for easy recognition and management.

  • Description (Optional): Additional details about the channel's purpose, recipients, or use case to provide context for other team members.

  • Channel Type: Select the appropriate notification method based on your communication requirements:

    Channel Type
    Description
    Required Field

    Email

    Direct email notifications

    Email ID: email address

    Slack

    Slack workspace integration

    Webhook URL: Enter stack webhook URL

    Webhook

    Custom HTTP endpoint integration

    Webhook URL: Enter webhook URL Headers (Add): Key/Value pair

    Microsoft Teams

    Microsoft Teams channel notifications

    Webhook URL: Incoming webhook URL

    OpsGenie

    Incident management and on-call alerting

    API URL: OpsGenie's API endpoint API Key: Access token for OpsGenie's API

  • Adding Multiple Channels: You can configure multiple notification channels for the same alert by clicking the Add button. This allows you to send alerts to different teams or systems simultaneously, ensuring comprehensive coverage and redundancy in your alerting strategy.

Use Existing Channels

Select from previously configured notification channels such as Slack, Microsoft Teams or Email.

Alert List

Once an alert is saved the same will be visible in the alerts page in tabular view.

Users can search the alert names from the search box provided at the top right corner of the alerts table list and filter the entire list.

Alert table columns should be interpreted as following:

  • Name: Alert name configured by the user while creating the alert.

  • Alert Severity: The Severity set by the user while creating the alert.

  • Channel Assigned: The communication channels that are configured to report the alerts.

  • Status: If the current alert is enabled or disabled. Whether it will send the alerts to configured channels or not.

  • Last Trigger: The last time the alert was triggered and notification was sent.

Alert Actions

On an alert user can perform certain actions which can be accessed by clicking on the three dots menu icon at the end of each alerts list row:

  • Edit Alert: Allows users to edit the alert rule. It will open the same Alert modal that was available while creating a new alert with form values pre filled.

  • Disable Alert: Allows users to stop the notifications from the alert.

  • Enable Alert: If an alert is disabled then only the user will see this option. This option allows the user to re-enable the notifications from the given alert.

  • Delete Alert: Delete the alert rule from the system and stop all notifications from the same.

Use the Create Alert button to create a new alert.

Last updated

Was this helpful?