Monitoring failed events

info

This documentation only applies to Snowplow BDP. See the feature comparison page for more information about the different Snowplow offerings.

📄️ Using the UI

Snowplow pipelines separate events that are problematic in order to keep data quality high in downstream systems. For more information on understanding failed events see here.

📄️ Setting up alerts

Overview

📄️ Using the API

As discussed in the section "Failed events in the Console", it is possible to view aggregates of failed events when you have turned on the respective optional functionality. This view makes it possible to quickly identify where most failed events are originating from -- as in what is the related app ID, what is the schema field that is misrepresented, etc. The API that powers this overview is publicly available and can be invoked with a valid token to feed your own monitoring systems if you wish.