Audit Log Fields
Audit logs capture authentication events and every change a user makes to platform configuration: users, groups, policies, dashboards, alert rules, scheduled views, pipelines, and more. Read-only operations are not recorded. Data queries are recorded separately in the performance logs. Every audit field is indexed as a Facet.
Finding Audit Logs
Each service writes its audit logs under its own source. Every audit entry carries the audit_log facet, so filter on that:
| Filter | What it selects |
|---|---|
|
All audit log entries across all services. Use this as the base filter for all audit queries. |
|
Audit entries from a single service |
The source tells you which service performed the action:
source |
Events recorded |
|---|---|
|
Login and logout events, MCP client authorization, users, groups, service accounts, policies, folders and folder permissions, dashboards, alert rules, silences, contact points, notification policies, and mute timings |
|
Derived metrics, logs pipelines, ingest auth keys, rate control, metric shaping rules, remap configuration, and federation membership |
|
Lookup tables, dimension tables, favorite facets, and scheduled views |
|
SLOs |
|
Archive management — Admin-only when RBAC is enabled, and audited starting with Release 4.3.0 |
|
Hydration jobs — Admin-only when RBAC is enabled, and audited starting with Release 4.3.0 |
|
Data deletion jobs |
|
Workbooks |
Any query service |
|
Events Captured
The action facet names the event and resource_type names what it acted on. Action values are written exactly as the service emits them, so some are lower-case and some are mixed-case.
action |
resource_type |
Trigger |
|---|---|---|
|
|
Successful login through SSO or basic auth |
|
|
User-initiated logout |
|
|
Failed login attempt on a locked account |
|
|
An MCP client registered itself for OAuth. |
|
|
A user completed the MCP OAuth login |
|
|
An MCP client exchanged an authorization code for a token |
|
|
An MCP client refreshed its token |
action |
resource_type |
Trigger |
|---|---|---|
|
|
A user account was created, modified, or deleted |
|
|
A group was created, modified, or deleted |
|
|
Group membership changed. |
|
|
A service account was created, modified, or deleted |
|
|
A service account token was issued or revoked |
action |
resource_type |
Trigger |
|---|---|---|
|
|
A policy was created, modified, or deleted |
|
|
A policy was mapped to, or unmapped from, a user or group |
|
|
A folder permission mapping was created, updated, or removed |
|
|
A request was denied because the caller lacked sufficient permissions |
action |
resource_type |
Trigger |
|---|---|---|
|
|
A folder was created or renamed |
|
|
A folder was deleted |
|
|
A dashboard was created, saved, or deleted |
action |
resource_type |
Trigger |
|---|---|---|
|
|
An alert rule was created, modified, or deleted |
|
|
An alert rule was paused or resumed |
|
|
A rule group was replaced in full, for example by a provisioning API call |
|
|
An alert silence was created |
|
|
A contact point was created, modified, or deleted |
|
|
The notification policy tree was changed |
|
|
A mute timing was deleted |
|
|
The Alertmanager configuration was reset |
action |
resource_type |
Trigger |
|---|---|---|
|
|
A lookup table was uploaded or replaced |
|
|
A dimension table was created |
|
|
A favorite facet was added, edited, or removed |
|
|
A scheduled view was created, edited, paused, resumed, or stopped |
action |
resource_type |
Trigger |
|---|---|---|
|
|
A derived metric was created, modified, deleted, paused, or resumed |
|
|
A logs pipeline was created, drafted, published, enabled or disabled, reordered, or deleted |
|
|
An ingest auth key label was created, modified, or deleted |
|
|
An ingest auth key token was issued or revoked |
|
|
A rate control policy was saved or deleted |
|
|
Rate control class label rules were saved or deleted |
|
|
A metric shaping rule was created, modified, or deleted |
|
|
The label remap configuration was changed |
action |
resource_type |
Trigger |
|---|---|---|
|
|
A remote cluster joined the federation |
|
|
Federation membership was changed |
|
|
An SLO was created, modified, or deleted |
|
|
A data deletion job was cancelled |
|
|
A workbook was created |
action |
resource_type |
Trigger |
|---|---|---|
|
|
An archive was created, edited, started, stopped, or deleted through the Archives screen or the archive REST API. Recorded for every attempt when audit logging is enabled, whether it was allowed or denied by RBAC. |
|
|
A hydration job was started, paused, resumed, or cancelled. Recorded for every attempt when audit logging is enabled, whether it was allowed or denied by RBAC. |
Facets
All audit log fields are indexed as Facets and appear in the Facets panel on the left side of the Logs UI. Clicking a facet value adds it immediately as a filter to the current query.
| Facet | Type | Values / Notes |
|---|---|---|
|
string |
Event name. See Events Captured. |
|
string |
Kind of resource acted on. See Events Captured. |
|
string |
Human-readable name of the affected resource: user email, group name, dashboard title, alert rule name, and so on |
|
string |
Unique ID of the affected resource. Falls back to |
|
string |
Email of the user who performed the action, or the service account name |
|
string |
Identity provider ID of the acting user |
|
string |
Role of the acting user: |
|
string |
|
|
string |
HTTP status code on failure, for example |
|
string |
Error detail on failure. |
|
integer |
How long the operation took, in milliseconds |
|
string |
Request identifier for cross-service correlation |
|
string |
Client IP address, taken from |
|
string |
HTTP User-Agent of the calling client |
|
string |
Additional context for the operation, present only on some events. For example, |
|
string |
Human-readable summary, for example |