Monitor status of your data pipelines and tracking plans in RudderStack.
RudderStack’s Health dashboard provides an intuitive UI to monitor all your Event Stream pipelines. It also provides realtime observability metrics for the tracking plans linked to your sources, including validation errors, violation types, etc.
To view this dashboard, log in to your RudderStack dashboard and go to Monitor > Health option in the left navigation bar.
Overview
In the Overview section, you get a quick summary of the destinations with failures across your Event Stream pipelines (both cloud and warehouse destinations). You also see the events with violations for all the tracking plans linked to your sources.
You can filter these metrics by period - one day, one week, or one month - depending on your requirement.
Event Stream destinations
This dashboard shows the event delivery and failure metrics only for cloud mode connections. It does not include data for the device mode connections.
See Connection modes for more details on cloud mode and device mode connections.
In this view, you get a list of all the Event Stream destinations in your workspace with the following details (along with the change percentage):
Events delivered
Failures
Failure rate
RudderStack provides a toggle to filter your destinations by Cloud and Warehouse. Click the Failures tab to view only the destinations that have event failures. By default, all the destinations are shown in this view.
You can also filter metrics for only the enabled/disabled destinations by clicking the filter option:
Destination-level event failure metrics
To get the destination-level data for event failures, click the row. A panel pops up on the right with details on the failed events.
Cloud destinations
RudderStack provides the following details for the failed events associated with the cloud destination:
Event name
Event type (identify, track, page, etc.)
Source
Count: Number of failed events.
Last happened: When the error last occurred.
Click the event to see a sample failed event payload along with corresponding error details. For more details, click the View Destination button on the top right.
Warehouse destinations
RudderStack provides the following details for the failed events associated with the warehouse destination:
Staging events: These correspond to the errors that occur in the staging process (during transformation or object storage, for example) before the syncs actually start. You will see the following details:
Event name
Event type (identify, track, page, etc.)
Source
Count: Number of failed events with the Event name.
Last happened: When the error last occurred.
Click the event to see a sample failed event payload along with corresponding error details. For more details, click the View Destination button on the top right.
Syncs: These correspond to the errors that occur during the warehouse syncs. You will see the following details:
Error category
Source
Events count
Syncs count
First happened
Last happened
Status
Click the event to see a sample error. You can also retry syncing the event to the warehouse by clicking the Retry all button.
(Current period count - Prior period count) / Prior period count * 100
Failures
(Current period count - Prior period count) / Prior period count * 100
Failure rate
Current percentage - Prior percentage
Here, period is the time period by which you want to filter the metrics - one day, one week, or one month.
Tracking plans
In this view, you get a list of all the sources connected to a tracking plan in your workspace with the following details (along with the change percentage):
Tracking Plan
Events validated
Violations
RudderStack also provides a Violations tab to view only the sources that have tracking plan violations.
Validation error details
To get the validation error details, click the source. A panel pops up on the right with the following details:
Event name
Event type (identify, track, page, etc.)
Events validated
Events dropped
Last occurred: When the error last occurred.
Use the Version dropdown to view the above metrics by tracking plan version. This is helpful if your tracking plan has undergone revisions recently.
Click the event to see the violation type. You can also click the violation type to see a sample payload and violation description.
For more information on the above metrics and violation types, see the Tracking plans guide.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.