# Source Event Metrics


{{< customreadfile "/includes/event-metrics/reporting-latency.md" >}}

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

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

## Events ingested

The **Events ingested** section shows 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, you also see the following 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.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.

{{< customreadfile "/includes/event-metrics/two-hour-filtering-window.md" >}}

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

### Event flow graph

An event flow graph 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

The **Event details** section shows 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/event-details-source.webp" alt="Event details section" >}}

### Event metrics

The **Events** tab includes 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`. |
| Count | Number of events received in the selected time period. |
| Last seen | Time since the event last occurred. |

### Violation details

The **Violations** tab includes the following details:

| 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 a row to see the 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

The **Blocked** tab includes the following details:

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