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.
The Gateway pillar is everything about getting telemetry into axonpush: the resources that organise it, the credentials that authenticate it, and the wire formats that carry it.
Apps and channels
An app is a logical service. A channel lives inside an app and is the destination every event names. You create both from the dashboard or the API, and the SDKs and the wizard provision them for you.
Credentials
- API keys (
ak_) authenticate server-side code overX-API-Key. Mint, scope and revoke them here. A key can be pinned to an app and an environment. - Public ingest tokens (
pt_) authenticate browser and mobile clients overX-Public-Token, scoped to one channel and one environment. See Authentication.
Ingest paths
SDK
Python, TypeScript and .NET clients with framework integrations.
OTLP
Point any OpenTelemetry collector or SDK at axonpush over OTLP/HTTP.
Sentry DSN
Repoint an existing Sentry client by changing one environment variable.
Related
- Events model, what an event is once it lands
- Environments, how an ingest request resolves an environment
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.
Observe
Read one request end to end as a trace, search the logs and events underneath it, and aggregate many traces into volume, error rate, latency, tokens and cost.