Vetrix Docs

Operations

Operations pages keep a running Vetrix instance healthy: the runners that execute pipeline jobs, scheduled database backups, the container registry and the space it uses, the audit trail, instance-wide usage analytics, search indexing, and maintenance mode. They are for the administrators who look after the instance itself, not for people working in a single repository, and an individual page appears only when your account holds the matching permission.

Where to find it: open the admin area (your avatar menu in the top navigation bar, then Admin panel, or go to gitvetrix.com/admin), then open the Operations group in the admin sidebar.

  • Analytics — instance-wide usage metrics with charts and leaderboards over a time range you choose, narrowed by user, event source, or event name.
  • Audit Log — the newest-first record of security- and administration-relevant events, filterable by actor, action, and date, with per-event detail and CSV export.
  • Backups — scheduled database backups, each pairing a cron schedule with a destination and a retention policy, with on-demand runs, run history, and restore.
  • Maintenance — take the instance offline for everyone except administrators and set the message shown on the maintenance page.
  • Registry — the instance-wide view of every container image, where you search and delete tags or whole images and review storage use and garbage collection.
  • Runners — register the machines that execute pipeline jobs, copy each runner's one-time registration token, watch its status, and deregister it when you retire it.
  • Search index health — the indexing queue's depth and last run, with controls to sweep everything back into the queue and to release stranded or retry-exhausted entries.