Destination Event Metrics

Get detailed metrics on event delivery.

Important consideration

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

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

Events tab for destinations in RudderStack dashboard

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-hour filtering window is available only in RudderStack’s Growth and Enterprise plans.

For Free plan users, the default filtering window is 1 day.

Event filtering window options

The default filtering option varies with the RudderStack plan:

RudderStack planDefault filtering window
Growth and Enterprise
  • Cloud destinations: 2 hours
  • Warehouse destinations: 1 day
Free
  • Cloud destinations: 1 day
  • Warehouse destinations: 1 day

Event delivery

This section covers observability metrics for cloud and warehouse destinations.

Cloud destinations

The Events delivery section includes the following metrics for cloud destinations:

  • 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 (only visible to Admins).

Event delivery trend

The Delivery tab shows how events were delivered to the cloud destination over the selected time period.

The graph only shows events sent in cloud mode - it doesn’t include the metrics from device mode and hybrid mode connections.

Event trends for destination

P95 latency

Note that:

  • The P95 latency metric is available only in RudderStack’s Enterprise plan
  • It is only applicable for cloud destinations connected to Event Stream sources

See P95 latency alerts to configure alerts for this metric.

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

Latency trends for destination

Factors affecting event delivery latency

One or more of the following factors can increase event delivery latency:

FactorNotes
Connection to multiple sourcesIf a destination is connected to two sources wherein one source has a significantly higher event volume than the other, then the high volume of one source can impact the delivery latency of the events coming from the other source.
Destination response timeDelivery speed depends on the destination API’s performance. Destination rate limits and downtime can impact delivery latency.
Transformation connection, time, and complexity
  • A destination connected to multiple sources and a transformation can have a higher delivery latency compared to a destination connected to the same sources without a transformation.
  • A complex and/or long-running transformation can cause delays in event processing, which can increase latency.
Handling volume spikes and cluster scalingRudderStack dynamically scales its clusters up or down to handle sudden spikes or any variations in event volume. During this process, it may temporarily pause event processing to balance the load across nodes, ensuring the events are processed in the correct order. While this safeguards data integrity, it may create a temporary event backlog and impact the delivery latency.

Contact the RudderStack team to learn more about provisioning for spikes.

Warehouse destinations

The Event delivery section includes the following metrics for warehouse destinations:

  • 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

The Delivery tab shows how events were delivered to the warehouse destination over the selected time period.

The graph only shows events sent in cloud mode - it doesn’t include the metrics from device mode and hybrid mode connections.

Warehouse destination events trend

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. The frequency of these syncs is configurable via the Sync Frequency connection setting for the warehouse destination.

Sync duration trends for warehouse destination

Event details (Event Stream)

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

The following table lists all events sent to the cloud destination within the specified time period.

Column nameDescription
Event nameName of the event in case the type is track.
Event typeType of event, for example, identify, track, etc.
Successful deliveriesNumber of events delivered to the destination successfully.
Last successful deliveryTime since the last event was delivered to the destination successfully.
FailuresNumber of events that failed to reach the destination.
Last failureTime since the last event failed to reach the destination.
Event details section for cloud destinations

View failed event details

Required permissions

Admins have full access to view the delivery failure details.

Members must have the Destination Failure Samples PII permission to see the delivery failure details. Otherwise, they see the following message:

PII permissions message

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

Event failure details for cloud destinations

Delivery failures (Warehouse and RETL)

These metrics show the errors that caused delivery failure for:

Column nameDescription
Error categoryError that caused the delivery failures.
CountNumber of events that failed because of the error.
Last seenTime since the event that caused this error last occurred.
Delivery failure details

View delivery failure details

Required permissions

Admins have full access to view the delivery failure details.

Members must have the Destination Failure Samples PII permission to see the delivery failure details. Otherwise, they see the following message:

PII permissions message

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

Delivery failures error details

Questions? Let's figure it out together.

Join the RudderStack Slack community to connect with other users, customers, and the RudderStack team — or reach out for direct support.