Skip to content

Administration

The System section is where you manage access and keep the platform healthy. Most of it is set-and-forget.

The Access page shows how sign-in is configured and who can do what. There are three roles:

  • Viewer — read everything: services, traces, logs, metrics, infrastructure, dashboards, alerts.
  • Editor — everything a viewer can do, plus create and change alert rules, notification channels, log-pipeline rules, and dashboards.
  • Admin — full control, including access settings, retention, backups, and upgrades.

Sign-in can be an open install (no auth, for a trusted network), a built-in local admin, or single sign-on through your identity provider, with your groups mapped to the roles above. Setup lives in Authentication.

The Audit page (admin only) is a searchable record of control-plane activity — who signed in, what was changed, and what was denied — filterable by time, category, outcome, and actor. It’s built to forward into your SIEM.

On the Retention page you set how long traces, logs, and metrics are kept, per type. Your data, your rules — keep more of what matters and less of what doesn’t.

The Backups page lets you snapshot your datastore on a schedule or on demand, and restore from a snapshot when you need to (a restore is confirmation-gated so it can’t happen by accident). See Backups to enable scheduling.

The Updates page shows your installed version against the latest on your release channel, with release notes. When enabled, it can perform a verified upgrade at the click of a button — or on a weekly maintenance window you choose — so staying current is hands-off. Every upgrade is cryptographically verified before it’s applied; see Verifying signed artifacts and the lifecycle manager.