# IRPCEventsAdmin.IsEventLoggingEnabled

Location: [gRPC API](https://developer.m-files.com/APIs/gRPC-API/index.md) > [Administration API](https://developer.m-files.com/APIs/gRPC-API/admin/index.md) > [Event administration](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEventsAdmin/index.md)

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

Badges: `Administration API / specialized` `admin` `session` `idempotent`

Tells whether event logging is on in the vault.

- **Service:** [Event administration](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEventsAdmin/index.md) `MFiles.IRPCEventsAdmin`
- **gRPC method:** `/MFiles.IRPCEventsAdmin/IsEventLoggingEnabled`
- **HTTP (mf-http-grpc):** `POST /grpc/v1/is-event-logging-enabled`
- **Request:** [`IsEventLoggingEnabledRequest`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEventsAdmin/IsEventLoggingEnabled/index.md#request)
- **Response:** [`IsEventLoggingEnabledResponse`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCEventsAdmin/IsEventLoggingEnabled/index.md#response)
- **Book and level:** Administration API, specialized
- **Kind:** admin
- **Session:** Required: the session ID from LogIn in the mfiles-session-id-bin metadata.
- **Idempotent:** yes
- **Returns metadata structure version:** no
- **Streaming:** none (unary)

<a id="remarks"></a>

## Remarks

- Requires a vault session and the vault right `manage_events` (a normal user is
  denied).

<a id="request"></a>

## Request: IsEventLoggingEnabledRequest

No fields.

<a id="response"></a>

## Response: IsEventLoggingEnabledResponse

> Nested message fields are expanded to depth 3; follow a type link for deeper levels and for the type's own page.

| Field | Type | Description |
|---|---|---|
| `enabled` | `bool` | True if the vault logs events. |