Skip to main content
Telemetry is in early access. To turn it on for your workspace, book a call or ask in Discord.
Superlog stores logs, traces, and metrics as OpenTelemetry. Send them from your code, from a Collector you already run, or straight from your cloud provider.

​
Choose a source

Moving from another vendor? See the migration guides for Datadog, New Relic, and Dynatrace.

​
Ingest endpoint

Code and Collectors send OTLP over HTTP to your region’s endpoint:
  • Send to /v1/logs, /v1/traces, or /v1/metrics under the endpoint. OpenTelemetry SDKs and the Collector add these paths for you.
  • Send the ingest key as x-api-key: <key> or Authorization: Bearer <key>.
  • Use http/protobuf or http/json. Gzip is supported. gRPC is not.
  • A request can be up to 8 MB.

​
Ingest keys

An ingest key decides which workspace the data goes to. Keys start with sl_ingest_. Create one from Overview in the sidebar. See Create an ingest key. Settings → Ingest keys lists each key and when it last sent data. Revoke a key there to stop it. Vercel and AWS sources create their own keys, and removing the source revokes its key.

​
Name your services

Set these resource attributes on every service. Superlog groups and filters your data by them. With an OpenTelemetry SDK, set them with OTEL_SERVICE_NAME and OTEL_RESOURCE_ATTRIBUTES.