# Event log (IRPCEventLog)

Location: [gRPC API](https://developer.m-files.com/APIs/gRPC-API/index.md) > [Vault API](https://developer.m-files.com/APIs/gRPC-API/vault/index.md)

HTML version: https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEventLog/

Writes custom entries to the vault's event log.

- **gRPC service:** `MFiles.IRPCEventLog`
- **Book and level:** [Vault API](https://developer.m-files.com/APIs/gRPC-API/vault/index.md), standard
- **Methods:** 1
- **Proto file:** [`mfiles/IRPCEventLog.proto`](https://developer.m-files.com/APIs/gRPC-API/downloads/proto/mfiles/IRPCEventLog.proto)

<a id="overview"></a>

## Overview

Applications and vault applications use
[AddCustomEventEntry](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEventLog/AddCustomEventEntry/index.md) to record their own
auditable events next to the events that M-Files Server writes itself (logins, object changes,
administrative changes). Reading and exporting the event log are administrative operations and
are not part of this service.

- Requires a vault session whose user has the vault right `generate_event_logs`
  ([VaultAccess](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.VaultAccess/index.md)).
- Nothing is written while event logging is disabled in the vault; the call still succeeds.

<a id="methods"></a>

## Methods

| Method | Summary | Facts |
|---|---|---|
| [AddCustomEventEntry](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEventLog/AddCustomEventEntry/index.md) | Adds a custom entry to the vault's event log and returns its event ID. | `write` `session` |