Skip to main content

The audit log

QA-Board records who did what, to what, when and from where: who started a batch on your runners, who deleted a run or changed its metrics, who signed in, created a token or changed a setting. Admins see everything in Admin → Audit; projects' developers and owners see their project's events in the project's Admin → Audit log (see the project's audit log).

Find who did something​

Open Admin → Audit. Events are newest first. Narrow them down:

  • Category or Action: e.g. Runs and batches, or only Deleted a batch.
  • By: part of a user name, e.g. ali finds alice.
  • About: what the event is about, e.g. batch:1234 or token. Click a name or a target in the list to filter on it.
  • From and To: the dates, both included.

Each event says who did it (and whether with a token), from which IP, and what changed. Details shows the rest: the commit and the runner of a batch started from the web app, the parameters of a tuning, how many runs were redone or deleted...

What is recorded​

  • Running code: batches and tunings started from the web app (with the runner, the commit and the parameters), runs redone, batches stopped, and CI jobs started from the web app (GitLab, GitHub Actions, Jenkins).
  • Deleting: batches, runs, milestones, files deleted from Storage usage or by the cleanup jobs, and old results deleted by the projects' retention (one event per project and cleanup).
  • Changing results: runs marked as failed, or whose metrics or status were edited, with their old and new values. Renamed and moved batches, and milestones.
  • Access: sign-ins (and failed ones), tokens, qa auth login approvals, users, groups, roles on projects, visibility and access requests.
  • Administration: settings, sign-in providers, storage locations, jobs and their schedules, and Celery workers reserved for remote sessions.

It never contains passwords or tokens: a changed secret is recorded as changed, never with its value, and parameters or CI inputs named like secrets (*_token, *password*, api_key...) are left out.

What isn't recorded, and why
  • Results sent by qa run, qa batch and qaboard.start_run(): each run already says who sent it, and with which token. Recording every call would flood the log.
  • Reading: opening pages, downloading files, exports. Usage analytics counts what people look at.
  • Personal preferences: favorites, settings in the web app.

Export it​

Export downloads the events matching the filters, as CSV or JSON Lines (one JSON object per line), up to 100,000 events at once: narrow the dates for more. Scripts get the same with an admin's token:

curl -H "Authorization: Bearer $QABOARD_TOKEN" \
"https://qaboard.example.com/api/v1/admin/audit?format=jsonl&since=2026-11-01&category=runs" > audit.jsonl

/api/v1/admin/audit takes action, category, actor, target_type, target_id, project, since and until (ISO 8601 dates), and returns pages of 100 events without format (follow next_before_id).

Send it to your SIEM​

With QABOARD_AUDIT_STDOUT=1, the backend also prints each event on its standard output once it's saved, as a line starting with qaboard-audit followed by the event as JSON. Your log collector (Fluent Bit, Vector, Splunk, a Kubernetes logging agent...) can forward these lines to your SIEM, where QA-Board's admins can't delete them. Events completed later, like a batch's final status, are printed again with the same id: keep the last line of each id.

Keep it for as long as you need​

Events are kept 730 days by default: change Keep audit events for in Admin → Settings → Security, and delete older events with qaboard-admin purge-audit from a scheduled job. Purging is itself recorded.

Behind a proxy, a load balancer or an ingress, set QABOARD_TRUSTED_PROXY_HOPS=1 so that events record your users' addresses, not the proxy's.

Limits
  • Events live in QA-Board's database: people who can write to it can change them. Forward them to a SIEM if you need a log they can't change.
  • Events before this version only cover sign-ins, tokens, admin changes and batch deletions.
  • Projects' members don't see the IP addresses and browsers in their project's audit log, nor the events of subprojects they can't see: only admins do.
  • CSV exports start cells like = with ', so that spreadsheets don't run labels as formulas.