Sending 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 ingest key scoped to your organization.
Mint an ingest key
In the Everr dashboard, open the user menu (top-left) and click Ingest Keys, then New key.
- Keys are organization-scoped: any data sent with the key is attributed to the organization it belongs to.
- The full key is shown 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-ingest-key>Requests without a valid key return 401 Unauthorized.
Tenant attribution
If you set an everr.tenant.id resource attribute in your SDK, it will be
stripped and overwritten with the value derived from your key. Tenant
identity comes from the key, not from the client.
Forwarding from your own collector
If you already run an OpenTelemetry Collector, point its OTLP exporter at Everr:
exporters:
otlphttp/everr:
endpoint: https://ingest.everr.dev
headers:
Authorization: "Bearer ${env:EVERR_INGEST_KEY}"Troubleshooting
- 401 — key is missing, malformed, revoked, expired, or not of kind
ingest. - 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.