Introduction to Alerts
At Hevo, providing visibility to our customers is important to us. In order to achieve this, architects at Hevo developed an intelligent alerts system. Hevo sends an alert when something happens that requires user attention.
Hevo sends alerts on email and slack - email is enabled by default - to enable slack alerts checkout this article. You can also manage alerts through Hevo Dashboard.
While there are multiple touchpoints, we enforce strict policies to ensure that we don’t flood you with unwanted alerts.
A user is notified when one of the following events occurs.
- Source Related Events - Whenever a source fails a notification is sent with the reason for failure. A notification is also sent when a failed source recovers.
- Destination Related Events - Whenever a destination fails a notification is sent with the reason for failure. A notification is also sent when a failed destination recovers.
- Pipeline Related Events - Whenever an action is taken on a pipeline by a colleague such as Creating, Deleting, Pausing and Resuming a Pipeline.
- Schema Related Events - Whenever any changes are made by a colleague on Schema Mappings or if we detect some new schemas to be mapped, we send notifications to all team members.
- Failed Events - We periodically send a summary of all the events that failed, along with the count of such events at an interval of 3 hours.
- Model Related Events - If a model fails, we send an alert to the user specifying the reason for the failure.
- Internal Errors - Engineers at Hevo try their best to provide the best experience to their users. Though very rare, Hevo encounters internal problems and it’s our responsibility to inform the user about the same. We keep track of such errors through our internal channels as well and try to fix such issues as soon as they arise.