Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-03

Audit log

The /auditoria screen — the record of who did what, when, on which resource, and how much it cost.

On this page (12)

The event log records what happened in the workspace. The cost values shown per event are estimates; the amount charged is the one on the invoice.

Screen walkthrough

The label of each button and what you should see at the end are in Audit log screen.

The Audit log screen (/auditoria) is the workspace trail: every relevant action becomes an event with who did it, when, on what, and how much it cost. As soon as you run queries or pipelines or change settings, it shows up here.

What it is#

A chronological record of the workspace events (most recent first), with filters and a table or log view. It's the basis for investigation, cost checks, and compliance requirements.

What it's for#

  • Finding out who triggered an action and when.
  • Checking the cost tied to expensive operations (query, refresh, AI, export).
  • Investigating failures (events flagged as error).

Who does it and when#

  • It's an owner area: it requires requireOwnerArea. An invited member is sent back to the BI workspace.
  • Use it when investigating an unexpected cost, a settings change, or a pipeline failure.

What the screen shows#

Each event includes: date/time (in UTC, log format), user (name/email), category, action, resource, detail, the SQL (when there is one, click to expand), and the estimated cost in R$.

Categories:

CategoryCovers
Useractions taken by people (login, editing, export…)
Systemautomatic platform events
Pipelineingestion/transformation runs
Billingbilling, monthly allowance, top-up
Securitysensitive events (MFA, permissions, access)

Available filters#

  • Text search (action, resource, user, detail, SQL).
  • Category, user, and resource (lists built from what exists in the events).
  • Derived status: OK or error (inferred best-effort from the action/detail — it's not a dedicated field).
  • Period (date + time), defaulting to the last 7 days.
  • Toggle between the Table view and the Log view.

The screen loads the workspace's last 200 events; the filters act on that window.

Step by step (investigating a cost)#

  1. Open /auditoria.
  2. Filter by period (e.g., yesterday) and, if you like, by user.
  3. Look for events with a high cost; click the SQL to see the full query.
  4. Cross-check with Lineage if you need to understand where the number came from.

Expected result#

A filterable list that answers "who, when, what, and how much it cost" for every action in the workspace.

Example#

At Comércio Aurora, the owner filters the Pipeline category for the last 7 days, finds a run flagged as error on prd_aurora_silver.vendas, expands the detail, and confirms that the source came in empty that day.

Limits and costs#

  • Opening the screen: R$ 0 — it reads the record from the database, not a paid query.
  • It shows the last 200 events; larger windows aren't paginated on this screen.
  • The cost per event is an estimate; the amount charged is the one on the invoice.
  • The OK/error status is derived from the action/detail text, not a guaranteed field.

Security#

  • Scoped by workspaceId; the screen is restricted to the owner.
  • The recorded SQL helps audit expensive or improper queries.

Common errors#

SymptomLikely causeWhat to do
"No events yet"new workspace/no activityrun a query or a pipeline and come back
I can't see old eventswindow limited to 200filter by a more recent period
I was sent to the BI workspacethe screen is an owner areasign in with an owner/admin account
Event cost looks different from the invoicethe value is an estimate (projection)treat it as a projection, not the final invoice

Related#


Last reviewed: 2026-09-08.

Related links