# 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.

{{< info >}}
The event metrics covered in this guide may not reflect real-time events due to reporting latency.
{{< /info >}}

## Source events

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

{{< image src="images/data-governance/event-blocking/blocked-event-metrics-source.webp" alt="View blocked event metrics for the source" >}}

### Events ingested

This section gives you observability into the following metrics:

- Number of events ingested and [blocked]({{< ref "data-governance/event-blocking.md" >}}) by the source.
- Number of [bot events]({{< ref "data-governance/bot-management.md" >}}) ingested and blocked by the source.
- If you have a [Tracking Plan]({{< ref "data-governance/tracking-plans/" >}}) 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]({{< ref "data-governance/tracking-plans/violation-management.md#violation-types" >}}).
    - Number of events dropped as a result of these violations.

{{< image src="images/dashboard-guides/event-metrics/events-ingested-view.webp" alt="Events Ingested view" >}}

##### **Filtering window**

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

{{< info >}}
The 2 hours filtering window is available only in RudderStack's [Growth](https://www.rudderstack.com/pricing/) and [Enterprise](https://www.rudderstack.com/enterprise-quote/) plans.

For the RudderStackFree plan users, the default filtering window is 1 day.
{{< /info >}}

{{< image src="images/dashboard-guides/event-metrics/event-filtering-window.webp" alt="Event filtering window options" >}}


##### **Event flow graph**

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

{{< image src="images/dashboard-guides/event-metrics/source-events-flow.webp" alt="Event flow details" >}}

### 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.

{{< image src="images/dashboard-guides/event-metrics/source-event-details.webp" alt="Event details section" >}}

#### Event metrics

You will see the following details under the **Events** tab:

| Column name | Description |
| :---| :----|
| Event type | Type of event, for example, `identify`, `track`, etc. |
| Event name | Name of the event in case the type is `track`. |
| Count  | Number of events received in the selected time period. |
| Last seen | Time since the event last occurred. |

#### Violation details

You will see the following details under the **Violations** tab:

| 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. | 
| Events validated | Number of events validated against the connected Tracking Plan. | 
| Events with violations | Number of events containing any [Tracking Plan violations]({{< ref "data-governance/tracking-plans/violation-management.md#violation-types" >}}). |
| Events dropped | Number of events dropped as a result of violations. | 
| Last seen | Time since the event that caused the violation last occurred. |

Click on a row to see the detailed violation details, including the [violation type]({{< ref "data-governance/tracking-plans/violation-management.md#violation-types" >}}) and a sample payload.

{{< warning >}}
**Required permissions**

[Admins]({{< ref "access-management/member-management.md#member-roles" >}}) have full access to view the Tracking Plan violation details.

[Members]({{< ref "access-management/member-management.md#member-roles" >}}) must have the [**Tracking Plan Violation Samples**]({{< ref "access-management/policies-overview.md#pii-permissions" >}}) PII permission to see the violation details.
{{< /warning >}}

{{< image src="images/dashboard-guides/event-metrics/source-violation-details.webp" alt="Source violation details" >}}

#### Blocked events

You will see the following details under the **Blocked** tab:

| Column name | Description |
| :---| :----|
| Event name | Name of the blocked event. |
| Block count | Number of times the event was blocked. |
| Last blocked | Time since the event was last blocked by RudderStack. |

## 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.

{{< 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.  

{{< info >}}
The 2 hours filtering window is available only in RudderStack's [Growth](https://www.rudderstack.com/pricing/) and [Enterprise](https://www.rudderstack.com/enterprise-quote/) plans.
{{< /info >}}

{{< image src="images/dashboard-guides/event-metrics/destination-events-filtering-window.webp" alt="Event filtering window options" >}}

Note that 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/) | <ul><li>Cloud destinations: 2 hours</li><li>Warehouse destinations: 1 day</li></ul> |
| Free | <ul><li>Cloud destinations: 1 day</li><li>Warehouse destinations: 1 day</li></ul> |

### 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 (only visible to [Admins]({{< ref "access-management/member-management.md#member-roles" >}})).

##### **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]({{< ref "destinations/rudderstack-connection-modes.md#cloud-mode" >}}) - it does not 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**

{{< 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**

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

| 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 | RudderStack's delivery speed is dependent on the destination API's performance. Destination rate limits and downtime can impact delivery latency. |
| Transformation connection, time, and complexity | <ul><li>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.</li><li>A complex and/or long-running transformation can cause delays in event processing, which can increase latency.</li></ul> |
| 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. <br /><br />[Contact](mailto:support@rudderstack.com) the RudderStack team to learn more about provisioning for spikes. |

#### 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](#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]({{< ref "destinations/rudderstack-connection-modes.md#cloud-mode" >}}) - it does not 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**

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]({{< 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 >}}

This section details all the 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

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" >}}

{{< warning >}}
**Required permissions**

[Admins]({{< ref "access-management/member-management.md#member-roles" >}}) have full access to view the delivery failure details.

[Members]({{< ref "access-management/member-management.md#member-roles" >}}) must have the [**Destination Failure Samples**]({{< ref "access-management/policies-overview.md#pii-permissions" >}}) PII permission to see the delivery failure details. Otherwise, they will see the following message:

{{< figure src="images/dashboard-guides/event-metrics/pii-permissions.webp" alt="PII permissions message" >}}
{{< /warning >}}

### Delivery failures (Warehouse and RETL) {#delivery-failures}

These metrics give you visibility into 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

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" >}}

{{< warning >}}
**Required permissions**

[Admins]({{< ref "access-management/member-management.md#member-roles" >}}) have full access to view the delivery failure details.

[Members]({{< ref "access-management/member-management.md#member-roles" >}}) must have the [**Destination Failure Samples**]({{< ref "access-management/policies-overview.md#pii-permissions" >}}) PII permission to see the delivery failure details. Otherwise, they will see the following message:

{{< figure src="images/dashboard-guides/event-metrics/pii-permissions.webp" alt="PII permissions message" >}}
{{< /warning >}}

## 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]({{< ref "transformations/templates.md#allowlist" >}}) 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).

{{< info >}}
The 2 hours filtering option is available only in RudderStack's [Growth](https://www.rudderstack.com/pricing/) and [Enterprise](https://www.rudderstack.com/enterprise-quote/) plans.

For the Free plan users, the default filtering window is 1 day.
{{< /info >}}

{{< image src="images/dashboard-guides/event-metrics/transformation-events.webp" alt="Events tab for transformations in RudderStack dashboard" >}}

### Event flow

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

{{< image src="images/dashboard-guides/event-metrics/transformation-events-trend.webp" alt="Event trends for transformation" >}}

### Transformation errors

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

| Column name | Description |
| :---| :----|
| Event type | Type of event, for example, `identify`, `track`, etc. |
| Event name | Name of the event in case the type is `track`. |
| Source | Source from where the event was ingested. |
| Destination | Destination where the transformed event was to be forwarded. |  
| Event count | Number of events dropped due to tranformation error. |
| Last seen | Time since the event that caused the transformation error last occurred. |
| Status code | HTTP status code of the tranformation error. |

{{< image src="images/dashboard-guides/event-metrics/transformation-errors.webp" alt="Transformation errors" >}}

#### View transformation error details

{{< warning >}}
**Required permissions**

[Admins]({{< ref "access-management/member-management.md#member-roles" >}}) have full access to view the transformation error details.

[Members]({{< ref "access-management/member-management.md#member-roles" >}}) must have the [**Transformation Failure Samples**]({{< ref "access-management/policies-overview.md#pii-permissions" >}}) PII permission to see the transformation error details. Otherwise, they will **not** see the **Details** option next to the errors, as shown:

{{< figure src="images/dashboard-guides/event-metrics/transformation-error-details-2.webp" alt="Transformation error details" >}}
{{< /warning >}}

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

{{< image src="images/dashboard-guides/event-metrics/transformation-error-details.webp" alt="Transformation error details" >}}