> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superlog.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Collect telemetry

> Every way to send logs, traces, and metrics to Superlog: OpenTelemetry SDKs, the browser SDK, a Collector, Vercel, AWS, and Google Cloud.

> [!NOTE]
>
> Telemetry is in early access. To turn it on for your workspace, [book a call](https://cal.com/superlog/yc) or ask in [Discord](https://discord.gg/wJ56aRh8hx).

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

| Source | Sends | Setup |
| - | - | - |
| [OpenTelemetry SDKs](https://docs.superlog.sh/guides/instrument-your-app.md) | Logs, traces, metrics | Ingest key and three environment variables. Node.js, Python, Go, Java, and any other OpenTelemetry SDK. |
| [Browser and React](https://docs.superlog.sh/guides/browser.md) | Errors, traces, page loads, Web Vitals | `@superlog/browser` with an ingest key. |
| [OpenTelemetry Collector](https://docs.superlog.sh/collect-telemetry/opentelemetry-collector.md) | Logs, traces, metrics | Add an `otlphttp` exporter. |
| [Vercel](https://docs.superlog.sh/collect-telemetry/vercel.md) | Traces, logs | Connect Vercel. Superlog creates the drains. |
| [AWS CloudWatch](https://docs.superlog.sh/collect-telemetry/aws.md) | Metrics, logs | Deploy a CloudFormation stack per region. |
| [Google Cloud](https://docs.superlog.sh/collect-telemetry/google-cloud.md) | Logs, metrics | Connect a project. Superlog reads from it. |

Moving from another vendor? See the migration guides for [Datadog](https://docs.superlog.sh/guides/migrate/datadog.md), [New Relic](https://docs.superlog.sh/guides/migrate/new-relic.md), and [Dynatrace](https://docs.superlog.sh/guides/migrate/dynatrace.md).

## Ingest endpoint

Code and Collectors send OTLP over HTTP to your region's endpoint:

| Region | Endpoint |
| - | - |
| EU | `https://superlog.sh/api/ingest` |
| US | `https://us.superlog.sh/api/ingest` |

* 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](https://docs.superlog.sh/guides/instrument-your-app.md#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.

| Attribute | Example |
| - | - |
| `service.name` | `checkout-api` |
| `deployment.environment.name` | `production` |
| `service.version` | `1.4.2` |

With an OpenTelemetry SDK, set them with `OTEL_SERVICE_NAME` and `OTEL_RESOURCE_ATTRIBUTES`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.