---
title: ProcessEventLogIndex
---

Since the [`ProcessEventLog`](./process-event-log.md) is a high-volume internal table, it has an associated index table that you can use to optimize administrative queries commonly performed against those tables: the `ProcessEventLogIndex`. The [Data Import Server](../../data-guide/dis.md) produces this Index table as it imports data, making it possible to identify the set of internal partitions that have data for a given key.

Using the index table can significantly reduce the time it takes to query the `ProcessEventLog` table, especially when you are looking for specific processes. See [Indexing Intraday Partitions](../table-storage/partition-indexing.md#consuming-partition-index-data) for more details.

## Columns

| Column Name         | Column Type | Description                                                                                                                       |
| ------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------- |
| `Date`              | String      | The date of the event.                                                                                                            |
| `InternalPartition` | String      | The column used to partition data.                                                                                                |
| `Process`           | String      | The name of the process that generated the event (e.g., `RemoteQueryDispatcher`, `worker_1`).                                     |
| `ProcessInfoId`     | String      | The unique identifier for the worker, used for correlating log entries and tables.                                                |
| `AuthenticatedUser` | String      | The authenticated user (e.g., the user who logged in via password, SAML, etc.) that owns the worker.                              |
| `EffectiveUser`     | String      | The effective user (e.g., the "operate as" user if the authenticated user is using the "operate as" option) that owns the worker. |

## Related documentation

- [Internal tables overview](./internal-tables.md)
- [`AuditEventLog`](./audit-event-log.md)
- [`PersistentQueryConfigurationLog`](./persistent-query-configuration-log.md)
- [`PersistentQueryStateLog`](./persistent-query-state-log.md)
- [`ProcessEventLog`](./process-event-log.md)
- [`ProcessInfo`](./process-info.md)
- [`ProcessMetrics`](./process-metrics.md)
- [`QueryOperationPerformanceLogCoreV2Index`](./query-operation-performance-log-index.md)
- [`QueryOperationPerformanceLogCoreV2`](./query-operation-performance-log.md)
- [`QueryPerformanceLogCoreV2`](./query-performance-log.md)
- [`QueryUserAssignmentLog`](./query-user-assignment-log.md)
- [`ResourceUtilization`](./resource-utilization.md)
- [`ServerStateLogIndex`](./server-state-log-index.md)
- [`ServerStateLog`](./server-state-log.md)
- [`UpdatePerformanceLogCoreV2Index`](./update-performance-log-core-index.md)
- [`UpdatePerformanceLogCoreV2`](./update-performance-log-core.md)
- [`WorkspaceDataSnapshot`](./workspace-data-snapshot.md)
- [`WorkspaceData`](./workspace-data.md)