Skip to main content
Version: 1.6.7

Configuration

orbit.Config is bound from the modules.orbit.* subtree of your nucleus.yml (or set directly in Go). Every field is optional — the zero value mounts a working panel under /admin.

The tables below group the keys by what they affect.

Mounting

Key (modules.orbit.*)TypeDefaultDescription
prefixstring/adminURL path Orbit mounts under.
titlestringHeading shown in the UI.
environmentstringLabel shown in the UI (e.g. production).

The bootstrap admin user

Key (modules.orbit.*)TypeDefaultDescription
bootstrap_usernamestringAdmin user created on first boot.
bootstrap_emailstringEmail for the bootstrap user.
bootstrap_passwordstringPassword for the bootstrap user. Leave it empty to skip bootstrapping entirely and provision the admin user another way, e.g. nucleus createuser.
auth_databasestringapp defaultDatabase alias whose handle backs admin login and the bootstrap user — point it at a dedicated database to keep the admin user store away from application data. Only login and bootstrapping are redirected; the panel itself always reads through the application's default handle.

Data and views

Key (modules.orbit.*)TypeDefaultDescription
migrations_pathstringmigrationsDirectory the migrations view reads.
audit_max_sizeint10000In-memory audit-log ring size.
multitenant_enabledboolfalseFilter records by the request's resolved tenant.
multitenant_defaultstringDefault tenant when none is resolved.
multitenant_ids[]stringKnown tenant IDs for the selector UI.

The live feed

Key (modules.orbit.*)TypeDefaultDescription
live_exclude_patterns[]stringPath patterns excluded from the live HTTP feed — use it to keep health checks and static assets out.
trace_url_templatestringExternal trace-explorer URL template, to deep-link each entry (supports {trace_id}).

The live-feed relay (the cluster_* keys)

By default the live feed shows this node's traffic. Turn these keys on and the nodes of one application relay their live events to each other over Redis, so the panel on any node shows the whole set.

Key (modules.orbit.*)TypeDefaultDescription
cluster_enabledboolfalseAggregate the live feed across nodes via a Redis relay.
cluster_redis_urlstringRedis URL for the relay.
cluster_channelstringnucleus:admin:live:v1Pub/sub channel for the relay.
cluster_node_idstringruntime idExplicit node identifier in the relay.
cluster_tokenstringShared secret to reject untrusted relay messages.
These keys are not the fleet plane

The cluster_* keys stay inside your application process: same panel, same binary, one shared feed. The standalone agent-and-server fleet plane is a different, heavier option — a dedicated observability server that application nodes stream to, with no Redis involved. Most applications need neither.

Example

# nucleus.yml
modules:
orbit:
prefix: /admin
title: Acme Admin
environment: production
bootstrap_username: admin
bootstrap_email: admin@acme.test