Skip to main content

Health Dashboard

A graphical interface to monitor the health of your datasets.

Jon Tam avatar
Written by Jon Tam
Updated over 3 months ago

Crux Health Dashboard is a monitoring tool that allows you to view the point-in-time health status of your datasets based on the latest data delivery to target destinations.

Why do you need the health dashboard?

Instead of reaching out to the Crux Support team to understand the status of your datasets, you can use this feature to not only stay on top of the flow of your Crux-processed data but also be proactive with downstream internal systems and models to help drive alpha. If an issue arises with one of your datasets, you can identify the underlying reason and, if you have the Crux Managed Service plan, track what Crux is doing to remediate the issue.

Getting started

To get started with the Health Dashboard, log into the Crux app, and Crux will take you to the Health Dashboard. If you are on another page in the app, click the Health Dashboard icon in the global navigation menu.

What is dataset health?

Crux's mission is to make the world's external data model ready. We understand that you need to effortlessly determine whether your data pipelines are running smoothly across all key stages of data flow: ingestion, processing, and delivery. Here are the statuses that the Health Dashboard displays to help you determine if data will be available at the destination promptly to prevent downstream disruptions.

Healthy datasets mean the latest data delivery ran successfully and on time (per the expected delivery schedule deadline configured upon data onboarding).

Late datasets mean that the most recent data delivery ran successfully but arrived at the destination after the expected delivery schedule deadline.

Missed datasets mean that the expected delivery schedule deadline has passed, and no data has arrived at the destination yet.

The underlying reasons for a Missed delivery could include:

  • The supplier never made the file available, and the pipeline run never started.

  • Crux is still processing the data after the expected delivery schedule deadline and no data has landed in the destination yet.

If Crux is still processing data and it arrives late, this health status will change from Missed to Late after it arrives.

Failed datasets mean that the most recent attempt at data delivery experienced a failure of some sort. This could range from 1) failing to ingest the file from the supplier, 2) failing to process the data correctly (perhaps due to a corrupt file) or 3) failing to dispatch the data to the target destination. Dataset failures are accompanied by summarized error messages explaining what occurred, using the Crux platform's best guess.

If you are a Managed Service user, Crux will be addressing this failure with high priority and you will be notified with updates by a Crux support member.

You may hover over the health status quick filters to get a definition of the meaning of each status.

Search datasets

Use the Search box to identify datasets by name. This may include any set of characters within the dataset name.

If you get no or unexpected results, try different keywords to find what you are looking for.

Filter datasets

You can find your datasets of interest based on their most recent health status.

You may click on more than one quick filter if needed.

Sort datasets

By default, your datasets are sorted by Latest Delivery in descending order and health status (with high-priority issues appearing first). Clicking on the column header for either Status or Latest Delivery will update the sort from highest to lowest priority or descending to ascending, respectively.

Recent delivery statuses

Although the latest delivery determines a dataset's overall health status, the Health Dashboard table displays the last ten most recent delivery attempts based on pipeline runs for a dataset's configured schedule. These recent deliveries are shown as circles, with the specific delivery attempt having the matching health status color.

The circle furthest to the right represents the most recent delivery, and subsequent circles to the left represent the descending order of deliveries.

Dotted circles mean the dataset was recently onboarded, and only the deliveries before that point were made. Datasets with only dotted circles mean the first pipeline run has yet to occur.

Viewing recent delivery status information can be done by hovering on one of these circles. This information tooltip includes the delivery status and timestamps for 1) when Crux retrieved the data, 2) when Crux processed the data, and 3) when Crux delivered the data to your destination.

⚠️ Note that status values can change over time. A Failed status can switch to Healthy if the dataset delivery is rerun successfully, or to Late if data remains overdue. Missed dataset deliveries may change to Late if the supplier publishes the data after the scheduled time but before the configured deadline.

View more details

To view more details about a dataset, click on its table row. This will open a sidebar with additional information related to that dataset, including details about the latest delivery and other key dataset metadata.

Latest failures

Datasets with the latest delivery failure will provide a brief explanation of the root cause. The step pertinent to the failure will display error or warning details. These can range from errors in ingesting the data from the supplier to errors in processing data due to unexpected file formats.

View support tickets

✨ This feature requires a Sphere by Managed Service subscription.

For datasets with the latest delivery failure, visit your org's incident requests page to view the support ticket applicable to the delivery failure. Click the View Support Ticket button in the dataset details tray to open a new browser tab and review the corresponding support ticket details.

🔐 You will need your Zendesk login credentials to access support ticket details. If you need assistance, contact your Crux administrator or email [email protected].

Destinations with Shares configurations

✨ This feature requires a Sphere by Managed Service subscription.

You may receive your data via target destinations configured in the Crux app. With the Sphere by Managed Service plan, you may elect to consume data via database shares (Snowflake, Databricks, BigQuery) where Crux hosts your data and can replicate it via the shares technology. If you are interested, please reach out to Crux for more information.

Did this answer your question?