Crux sends automated, real-time system alerts any time a monitored event occurs. Depending on the event type, a notification communicates an information notice about your dataset delivery. You can customize:
Resources you would like to monitor
Events to monitor for and trigger a notification
Distribution channel to use to deliver notifications
Resources
Crux monitors data health on a dataset level. Dataset health is designed to be consistent with health statuses on the Health Dashboard. When you configure monitoring a dataset, once the dataset is activated for regular deliveries, you will be able to receive notifications informing you on the state of data flow with respect to its scheduled deadline. It answers the questions of where is my data and is it on time?
Events
The following is an inventory of monitored events that can trigger a real-time notification.
Missed delivery
All datasets are configured with a configured deadline of when data should arrive at a target destination. Missed delivery notifications indicate that a dataset deadline arrived and no data was delivered by this time. Data can be missing due to the Data Supplier failing to provide a resource at the source. It also could mean that Crux is still processing the data by the deadline; in this case, when Crux processed data arrives at the destination, it will be a Late delivery.
Late delivery
Late delivery notifications indicate that data was successfully delivered to a target destination, but it arrived after a dataset deadline. Data could arrive late due to the Data Supplier providing a resource at the source later than expected.
Failed delivery
Failure notifications indicate a critical error condition requiring immediate attention. When you receive a failure notification, it indicates where the issue has occurred and the cause of the failure. There are several reasons why a dataset might fail, such as if the source connection credentials have changed, a resource at the source was not updated, or the data file has become corrupted.
At Crux, we follow a four-step process called a workflow from ingestion to delivering a dataset from a single source to one or more destinations. The steps are ingestion, normalizing, processing, and delivery. A failure notification will indicate the exact step where and why the failure occurred.
Ingestion failure – There were issues connecting, retrieving, or downloading data from the source.
Normalizing failure – There were issues normalizing data.
Processing failure – There were issues with identifying the source data format or other processing challenges.
Delivery to the destination failure – There were issues during the final step of dispatching data to the destination. This could include connecting to the target destination for dispatch.
Success delivery
The workflow has been completed successfully, and the dataset has been updated with no issues.
Distribution Channels
Crux distributes notifications via the following channels:
Email
Webhooks
Google Cloud Pub/Sub
Amazon AWS SQS
You can add as many delivery channels as you prefer, and specify rules on when to use them. If you prefer receiving alerts via different technical integrations for the same incident, the same notification can be delivered via multiple channels. To learn more about configuring distribution channels, you can visit the Distribution Channels article.
Learn More
To learn more about Notifications visit: