Audit Log Data
Audit logs capture authentication and authorization mutation events on the Kloudfuse platform. Each entry is a JSON object whose fields are indexed as Facets.
Finding Audit Logs
You can find audit logs using either filter:
| Filter | What it selects |
|---|---|
|
All audit log entries across all services |
|
Equivalent; matches the raw field written into each log entry |
Use source="kf-audit-log" as the base filter for all audit queries.
Events Captured
Audit logs record mutation and authentication events. Read-only operations and queries are not recorded.
action value |
Trigger |
|---|---|
|
Successful login via SSO or basic auth |
|
User-initiated logout |
|
Failed login attempt on a locked account |
|
A remote cluster joined the federation |
action value |
Trigger |
|---|---|
|
A user account was created ( |
|
A user account was modified, including query priority changes |
|
A user account was deleted |
action value |
Trigger |
|---|---|
|
A group was created ( |
|
A group was modified |
|
A group was deleted |
|
A user was added to a group |
|
A user was removed from a group |
action value |
Trigger |
|---|---|
|
A service account was created ( |
|
A service account was modified |
|
A service account was deleted |
|
A service account token was issued |
|
A service account token was revoked |
action value |
Trigger |
|---|---|
|
A policy was created ( |
|
A policy was modified |
|
A policy was deleted |
|
A policy was mapped to an entity |
|
A policy mapping was removed |
|
A request was denied because the caller lacked sufficient permissions |
action value |
Trigger |
|---|---|
|
A folder permission mapping was created or updated ( |
|
A folder permission mapping was removed |
|
A dashboard folder was deleted |
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 |
|
|
string |
Email address of the user who performed the action |
|
string |
|
|
string |
|
|
string |
Human-readable name of the affected resource — user email, group name, policy name, and so on |
|
string |
|
|
string |
HTTP status code on failure (for example |
|
integer |
How long the operation took in milliseconds |
All Log Fields
In addition to the facets above, each audit log entry carries the following fields in the log body:
| Field | Type | Description |
|---|---|---|
|
string |
Unique ID of the affected resource; falls back to |
|
string |
Internal ID of the acting user |
|
string |
HTTP User-Agent of the calling client |
|
string |
Unique request identifier for cross-service correlation |
|
string |
Error detail on failure; |
|
string |
Additional context for the operation (varies by action type) |