Event Metrics

RudderStack gives you observability into events at various stages of the pipeline, specifically at:

• Event ingestion (Source)
• Transformation, and
• Event delivery (Destination)

This guide walks you through the different event metrics in detail.

The event metrics covered in this guide may not reflect real-time events due to reporting latency.

Source events

Click the Events tab in your source page to view detailed metrics for the ingested events along with their details.

Events ingested

This section gives you observability into the following metrics:

• Total events ingested by the source.

• If you have a tracking plan connected to the source, then you will also see the below details:

  • Number of events validated by the tracking plan.
  • Number of events containing tracking plan violations.
  • Number of events dropped as a result of these violations.

Filtering window

You can filter the above metrics for the past 2 hours, 1 day, 7 days, and 30 days.

The 2 hours filtering option is available only in RudderStack’s Starter, Growth and Enterprise plans.

Note that the default filtering option varies with the RudderStack plan:

Event flow graph

RudderStack also provides an event flow graph that highlights the event ingestion and processing trends over the selected time period.

Event details

This section gives you details on the ingested events and violations arising due to non-compliance with the connected tracking plan.

You can search for specific event names or sort all events by type, name, count, and last occurred.

You will see the following details under the Events tab:

You will see the following details under the Violations tab:

Destination events

Click the Events tab in your destination page to view detailed metrics for the events sent to the destination along with their details.

Filtering window

You can filter the event metrics by source and time period - past 2 hours, 1 day, 7 days, or 30 days.

The 2 hours filtering option is available only in RudderStack’s Starter, Growth and Enterprise plans.

Note that the default filtering option varies with the RudderStack plan:

Event delivery

This section covers observability metrics for cloud and warehouse destinations.

Cloud destinations

You will see the below metrics for cloud destinations in the Events delivery section:

• Total events delivered to the destination.
• Number of events that failed to deliver and the failure rate.
• P95 latency, that is, the maximum latency experienced by 95% of the events to reach the destination.

Event delivery trend

RudderStack also provides a detailed events trend in the Delivery tab that highlights how it delivered the events to the cloud destination over the selected time period.

Note that the graph only shows events sent in cloud mode - it does not include the metrics from device mode and hybrid mode connections.

P95 latency

Note that:

• The P95 latency metric is available only in RudderStack’s Starter, Growth and Enterprise plans.
• It is only applicable for cloud destinations connected to Event Stream sources.

Switch to the Latency tab to view the P95 latency trends for the cloud destination over the specified time period.

Factors affecting event delivery latency

The event delivery latency can be impacted by one or more of the following factors:

Warehouse destinations

You will see the below metrics for warehouse destinations in the Event delivery section:

• Total events delivered to the destination.
• Number of events that failed to deliver and the failure rate.
• Maximum sync duration for the specified time period. See Sync duration for more information on this metric.

Event delivery trend

RudderStack also provides a detailed events trend in the Delivery tab that highlights how it delivered the events to the warehouse destination over the selected time period.

Note that the graph only shows events sent in cloud mode - it does not include the metrics from device mode and hybrid mode connections.

Sync duration

Switch to the Sync duration tab to see the trends for maximum sync duration, that is, the longest sync duration for all the data syncs within each specified time bucket. Note that the frequency of these syncs is configurable via the Sync Frequency connection setting for the warehouse destination.

Event details

These metrics are shown only for cloud destinations connected to Event Stream sources.

This section details all the events sent to the cloud destination within the specified time period.

Click a row to see the event failure details along with the sample error and payload.

Delivery failures

These metrics give you visibility into the errors that caused delivery failure for:

• Warehouse destinations
• Cloud destinations connected to Reverse ETL sources

Click a row to see the event failure details along with the sample error and payload.

If you are on the Enterprise plan, make sure your PII access is not limited. Otherwise, you may not be able to see the event payload.

Transformation events

Click the Events tab in your transformation page to view detailed metrics for the events processed by the transformation. You will see the following details:

• Total events ingested for transformation.
• Number of events dropped intentionally by the transformation (because of the transformation’s logic). For example, if your transformation allowlists only track events with the name Product Purchased, any event that does not meet this criteria is dropped.
• Number of events dropped due to transformation errors.
• Number of events successfully transformed and forwarded for further processing.

Filtering window

You can filter the above metrics by source, destination, and time period (past 2 hours, 1 day, 7 days, or 30 days).

The 2 hours filtering option is available only in RudderStack’s Starter, Growth and Enterprise plans.

Note that the default filtering option varies with the RudderStack plan:

Event flow

RudderStack also provides a detailed event flow graph that highlights how it transformed the events over the selected time period.

Transformation errors

This section gives you visibility into the transformation errors. You will see the following details:

Click Details to see the error description and the payload that caused the error:

If you are on the Enterprise plan, make sure your PII access is not limited. Otherwise, you may not be able to see the event payload.

Questions? Contact us by email or on Slack