Production telemetry
Send OpenTelemetry traces, logs, and metrics to Everr from any SDK or collector.
Everr accepts standard OpenTelemetry (OTLP) traces, metrics, and logs from any SDK or collector. Telemetry is per-tenant: every request must be authenticated with an API key scoped to your organization that has the Send telemetry capability.
Sending from browsers?
Telemetry sent straight from web pages needs a public, origin-bound API key. See Browser telemetry.
Mint an API key
In the Everr dashboard, open the user menu (top-left) and click API keys, then New key.
- Select the Send telemetry capability: it's what lets the key authenticate OTLP requests.
- Keys are organization-scoped: any data sent with the key is attributed to the organization it belongs to.
- The full key is shown only once, at creation time. Copy it into your secret manager; you can't retrieve it later.
- Admins can revoke a key at any time. Revocation is effective within about 30 seconds (the collector's positive cache TTL).
Endpoints
| Protocol | URL |
|---|---|
| OTLP HTTP | https://ingest.everr.dev |
Send the key as a bearer token in the Authorization header:
Authorization: Bearer <your-api-key>Requests without a valid key return 401 Unauthorized.
Forwarding from your own collector
If your production infrastructure already runs an OpenTelemetry Collector, point its OTLP exporter at Everr. Everr's local collector remains local and never forwards to Cloud. Keep the local application's exporter configuration working separately from production.
exporters:
otlphttp/everr:
endpoint: https://ingest.everr.dev
headers:
Authorization: "Bearer ${env:EVERR_INGEST_KEY}"Troubleshooting
- 401: key is missing, malformed, revoked, expired, or lacks the Send telemetry (
ingest) capability. - 5xx: transient; the SDK should retry with backoff.
- Telemetry shows up under a different tenant than expected: confirm you're using the right key. The tenant attribute in your SDK config is ignored; only the key determines tenancy.