Skip to content

Observability

Observability

The Observability page answers two questions: who did what on the platform, and what the platform did on its own. It is for administrators (members of the admin group).

Audit tab

One row per request a user made: saving or running a job, changing a setting, reading a secret, signing in, pushing an image. Refused and failed requests are listed too, with their outcome.

  • Filter by time, user, action, resource, outcome, source (GUI, CLI, Python SDK, remote CLI) and environment.
  • Rows of one SDK deploy fold together behind its job save; the +N badge opens them.
  • Related platform events on a row shows what the platform did for that request: the build, the run, the containers.
  • Routine listing and status requests (dt job ls, page refreshes) are not recorded.

System activity tab

What the scheduler, builder and nodes did: a schedule registered or triggered, a build started, finished or failed, a job dispatched or blocked because no node had room, a container started or lost, a run finished. Problems only keeps the blocked and failed rows.

The same rows appear on a job's Events tab and on a run's timeline, for anyone who can read the job.

Export

Export downloads the rows matching the current filters as CSV or JSON, up to 10,000 rows. For more, the dialog shows the dt log command that pages through the full result.

From the CLI

dt log audit                       # the last 24 hours
dt log audit -u alice -A job.save  # one user, one action
dt log audit -O denied -S 2026-10-01T00:00:00Z
dt log audit -T 4bf92f35 --with-events   # one request, the build it started, the run it created
dt log events my-job               # the latest run of a job
dt log events --job-level my-job   # builds and schedules of a job
dt log events --all -O blocked,failed    # every problem, admins only

dt log audit --help and dt log events --help list every option. Add -j for JSON.

Retention

Audit rows are kept for 365 days by default. Change it in Settings (Audit log retention) or with:

dt settings put audit '{"retention_days": 730}'

The change reaches the log store within a minute and is itself recorded in the audit log.