# Destination Event Metrics {{< customreadfile "/includes/event-metrics/reporting-latency.md" >}} Click the **Events** tab on your destination page to view detailed metrics for the events sent to the destination along with their details. {{< image src="images/dashboard-guides/event-metrics/destination-events.webp" alt="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. {{< customreadfile "/includes/event-metrics/two-hour-filtering-window.md" >}} {{< image src="images/dashboard-guides/event-metrics/destination-events-filtering-window.webp" alt="Event filtering window options" >}} The default filtering option varies with the RudderStack plan: | RudderStack plan | Default filtering window | | :-----| :------ | | [Growth](https://www.rudderstack.com/pricing/) and [Enterprise](https://www.rudderstack.com/enterprise-quote/) | | | Free | | ## 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]({{< ref "access-management/member-management.md#member-roles" >}})). #### 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]({{< ref "destinations/rudderstack-connection-modes.md#cloud-mode" >}}) - it doesn't include the metrics from [device mode]({{< ref "destinations/rudderstack-connection-modes.md#device-mode" >}}) and [hybrid mode]({{< ref "destinations/rudderstack-connection-modes.md#hybrid-mode" >}}) connections. {{< image src="images/dashboard-guides/event-metrics/destination-events-trend.webp" alt="Event trends for destination" >}} #### P95 latency {#p95-latency} {{< info >}} Note that: - The P95 latency metric is available only in RudderStack's [Enterprise](https://www.rudderstack.com/enterprise-quote/) plan - It is only applicable for cloud destinations connected to [Event Stream sources]({{< ref "sources/event-streams/" >}}) See [P95 latency alerts]({{< ref "monitor/alerts.md#p95-latency-alerts" >}}) to configure alerts for this metric. {{< /info >}} Switch to the **Latency** tab to view the P95 latency trends for the cloud destination over the specified time period. {{< image src="images/dashboard-guides/event-metrics/destination-latency-trend.webp" alt="Latency trends for destination" >}} #### Factors affecting event delivery latency One or more of the following factors can increase event delivery latency: | Factor | Notes | | :--- | :----| | Connection to multiple sources | If 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 time | Delivery speed depends on the destination API's performance. Destination rate limits and downtime can impact delivery latency. | | Transformation connection, time, and complexity | | | Handling volume spikes and cluster scaling | RudderStack 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](mailto:support@rudderstack.com) 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](#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]({{< ref "destinations/rudderstack-connection-modes.md#cloud-mode" >}}) - it doesn't include the metrics from [device mode]({{< ref "destinations/rudderstack-connection-modes.md#device-mode" >}}) and [hybrid mode]({{< ref "destinations/rudderstack-connection-modes.md#hybrid-mode" >}}) connections. {{< image src="images/dashboard-guides/event-metrics/warehouse-destination-events-trend.webp" alt="Warehouse destination events trend" >}} #### Sync duration {#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]({{< ref "destinations/warehouse-destinations/bigquery.md#connection-settings" >}}) connection setting for the warehouse destination. {{< image src="images/dashboard-guides/event-metrics/warehouse-destination-sync-duration.webp" alt="Sync duration trends for warehouse destination" >}} ## Event details (Event Stream) {#event-details} {{< info >}} These metrics are shown only for cloud destinations connected to [Event Stream sources]({{< ref "sources/event-streams/" >}}). {{< /info >}} The following table lists all events sent to the cloud destination within the specified time period. | Column name | Description | | :---| :----| | Event name | Name of the event in case the type is `track`. | | Event type | Type of event, for example, `identify`, `track`, etc. | | Successful deliveries | Number of events delivered to the destination successfully. | | Last successful delivery | Time since the last event was delivered to the destination successfully. | | Failures | Number of events that failed to reach the destination. | | Last failure | Time since the last event failed to reach the destination. | {{< image src="images/dashboard-guides/event-metrics/event-details.webp" alt="Event details section for cloud destinations" >}} ### View failed event details {{< customreadfile "/includes/event-metrics/destination-failure-samples-permission.md" >}} Click a row to see the event failure details along with the sample error and payload. {{< image src="images/dashboard-guides/event-metrics/event-details-failure.webp" alt="Event failure details for cloud destinations" >}} ## Delivery failures (Warehouse and RETL) {#delivery-failures} These metrics show the errors that caused delivery failure for: - [Warehouse destinations]({{< ref "destinations/warehouse-destinations/" >}}) - Cloud destinations connected to [Reverse ETL sources]({{< ref "sources/reverse-etl/" >}}) | Column name | Description | | :---| :----| | Error category | Error that caused the delivery failures. | | Count | Number of events that failed because of the error. | | Last seen | Time since the event that caused this error last occurred. | {{< image src="images/dashboard-guides/event-metrics/delivery-failures.webp" alt="Delivery failure details" >}} ### View delivery failure details {{< customreadfile "/includes/event-metrics/destination-failure-samples-permission.md" >}} Click a row to see the delivery failure details along with the sample error and payload. {{< image src="images/dashboard-guides/event-metrics/destination-delivery-error.webp" alt="Delivery failures error details" >}}