The dashboard
A tour of the axonpush dashboard and its pillars, from getting traffic in through the gateway to observing, alerting, moderating and governing what your agents do.
The dashboard is where you watch what your agents did and act on it. Every surface is backed by the same API the SDKs and the MCP server use, so nothing here is a view you cannot also script.
The home screen is a read on the last 24 hours: events ingested, active traces, error rate and mean duration, with an activity chart and the most recent traces. From there the product is organised into pillars.
The dashboard reads GET /capabilities on load and only shows what your plan
and deployment grant. If a pillar below is missing, it is gated off rather than
broken, check the capability flags.
The pillars
Overview
The 24-hour read: volume, active traces, error rate, mean duration, and the most recent traces.
Gateway
How traffic gets in: apps, channels, keys and tokens, plus the SDK, OTLP and Sentry ingest paths.
Observe
Traces, logs and analytics. One request end to end, and the aggregates over many.
Alerts
Fire when a finished trace crosses a threshold, to email or a webhook endpoint.
Moderation
Rules over the content flowing through your agents, and the violations they catch.
Govern
Environments, telemetry policy, members and roles, export destinations.
Compliance
The audit log and the retention and privacy controls behind it.
Connect (MCP)
Connect a coding agent over MCP so it can provision and read traces for you.
Audit log
The append-only record of organisation-level change, what is captured, what is deliberately not, the entry shape, and how to page through it without misreading the totals.
Gateway
Where traffic gets in. Apps and channels organise your events, keys and tokens authenticate them, and the SDK, OTLP and Sentry paths carry them.