How-to
Watch the runtime
Once integrations are running, the job is to see volume, latency, and the work queue — then jump to the owning page.
Dashboard
Open the home Overview. Tiles are computed from the message ledger and the failure registry for the active tenant. There are no seeded numbers on a connected deployment.
| Tile | What it means |
|---|---|
| Messages | Ledger rows in the configured window, plus how many integrations are running |
| Delivery success | Delivered versus retried and dead-lettered |
| p95 latency | From ledger latency_ms when the deployment records it; otherwise n/a |
| Operator work queue | Unresolved failures, highest severity first |
Click a tile for the breakdown and a jump to Monitor. The Instance monitoring tab shows CPU, memory, disk, database, and runtime utilization plus retained trends.
The reporting window lives under Settings → Monitoring & retention. Widening it takes effect on the next read — no restart.
Logs
Monitor → Logs searches structured events by level, component, integration, and related message (queue_id:sequence). File sources are intentionally verbose: poll, skip, pickup, deliver, commit, and misconfiguration all show up even when nothing moved.
curl -s "$SIRIUS/logs?tenant_id=default&level=warn&q=timeout"
curl -s "$SIRIUS/logs?tenant_id=default&related_to=<queue_id>:<sequence>"
curl -s "$SIRIUS/operations/overview?tenant_id=default" | jq '.kpis'
curl -s "$SIRIUS/operations/instance/metrics"Log lists page with X-Next-Cursor. Walk until the header is absent. A bad cursor is 400 — the server will not silently restart at the top.
Retention
Two policies, both tenant-scoped:
- Monitoring & retention — dashboard window and instance-metrics capture (
GET/PUT /operations/monitoring/settings). - Log retention — window, legal hold, and purge (
GET/PUT /logs/policy).
Purge is an explicit operator action. Legal hold blocks it.
When a number looks wrong
- Empty tiles on a fresh tenant are honest — no traffic yet.
- Latency
n/ameans the ledger is not recordinglatency_msin this deployment, not that everything is instant. - A file poller that never picks up files is usually a path the runtime cannot see. See Add a connector.