If your installation does not record actions
The access log is an optional part of a Dippr installation, and it is off unless whoever deployed it turned it on. Permission to read it is granted the same way either way, so an administrator can hold the permission on an installation that records nothing. When that is the case the page says so: “The access log is not enabled on this installation”, with no table and no filters. That is not an error and not a permission problem, and it is a different statement from an empty log — an empty log means none of the recorded actions happened in the window you asked for, and this means none of them were ever recorded at all. The tab stops being offered once the page has established it. Ask whoever operates your installation to enable the audit service if you need an action trail.What each row shows
Rows are newest first. Role changes targeting a group show the group name recorded as its ID, taggedGroup. Group rows recorded before this tag existed are tagged Member.
What is recorded
Seventeen actions, and only these seventeen:
Fleet placement, plane egress and plane location entries are best effort; an audit outage does not block the change.
Anything not on that list leaves no row. Changing an integration, starting an engine or running a
query are all recorded elsewhere or not at all:
- Queries live in Activity → Queries, described in Query history.
- An engine’s own timeline (provisioned, suspended, catalogs applied) is on that engine’s page, and any member who can see the engine can read it.
What is not recorded
Refused attempts are not recorded in this version. The log shows actions that succeeded, so an empty or clean log means none of the recorded actions happened, not that nothing was attempted or blocked. The page says so above the table, and keeps saying it until the version you are running starts recording refusals. Removing a member is not recorded in this version. When a member is removed, all of their roles go with them, but no Role revoked row is written for those roles and no removal row is written either. A member who disappears from Settings → Users may therefore have no matching revoke row here.Narrowing the list
Three filters sit above the table.1
Time window
Defaults to the last 24 hours. The widest option reaches the full 365 days that are kept. A
narrow window is much cheaper to read, which is why the default is a day rather than everything.
2
Action
One of the seventeen actions above, or Any action.
3
Actor
An exact match on the id in the Actor column, not a name and not a fragment. Hover a row’s Actor
cell to see the exact value, and paste that. A partial value matches nobody and gives you an
empty page.
How long rows are kept
365 days. After that a row is dropped, and there is no way to recover it or to extend the window for rows already gone. Export what you need before the horizon if your own retention rules are longer. Rows are never edited or deleted before then: nothing in Dippr can remove an entry from this log.Who can read it
Reading the access log is a separate permission from reading members or roles, and no built-in member role holds it. Administrators hold it. See the Roles and permissions matrix for which built-in role grants what, and Roles and permissions for granting it to a role of your own.Related
Query history
The other screen under Activity: every query your engines ran.
Service users and API keys
Where keys are minted and revoked, which is what the apikey rows are about.