On This Page

Hevo provides you visibility into the running of your system through alerts. Alerts are sent to you whenever an incident that requires your attention occurs in the system.

Hevo can send alerts to an email address and a Slack channel. To receive alerts on Slack, however, you need to enable it. Read Getting Alerts in Slack to know how to enable the Slack integration. By default, all the alerts defined by you are sent to the configured email address.

You can manage alerts through the Hevo Dashboard. Hevo has strict policies and does not send you unwanted alerts.

Hevo sends alerts for the following type of incidents:

  • Source-related: Whenever a Source fails, that is, the Pipeline cannot ingest data from it, or when the Source recovers from a failure, a notification is sent.

  • Destination/Warehouse-related: Whenever a Destination or Warehouse fails or recovers from a failure, a notification is sent.

  • Schema-related: Hevo sends schema-related alerts in the following scenarios:

    • Whenever you drop a table in the Destination, Hevo deletes the corresponding mapping, and an alert is sent to all the team members.

    Note: If Auto Mapping is enabled, Hevo recreates the deleted table in the Destination during the next Pipeline run. If you don’t want this table to be created again, disable Auto Mapping.

    • Hevo sends you alerts whenever it resizes a decimal or string column in the Destination table. For example, suppose that your Destination table contains a string column with the size 20, and your Source data contains a string field with the size 40. Then, Hevo resizes the string column in the Destination table to a value greater than 40 and sends you an alert for it.
  • Ingestion and loading-related: Whenever the data loaded to the Destination exceeds the defined threshold, a notification is sent.

  • Failed Events-related: Hevo sends a summary of all the Events that failed, along with their count every 3 hours.

  • Model-related: Whenever a Model fails, a notification is sent with the reason for the failure.

  • Activation-related: Whenever an Activation run fails, or if an Activation fails to connect to the configured Target or Warehouse, a notification is sent with the reason for the failure. A notification is also sent when the Activation recovers from these failures.

  • Target-related: Whenever a Target fails or recovers from a failure, a notification is sent.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Oct-17-2022 1.99 Updated page to add about ingestion and loading-related alerts.
Apr-11-2022 NA - Added information about Activation related alerts.
- Organized the content for clarity and coherence.
Oct-04-2021 1.73 Updated the content to remove obsolete alerts.
Last updated on 17 Oct 2022

Tell us what went wrong