> ## 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.

# Set up Superlog

> Connect your telemetry, choose the repositories Superlog reads, choose a Slack channel for findings, and choose a plan.

Setup has five steps. It opens when you sign in to a new workspace, and stays under **Setup** in the sidebar.

**1. Connect your telemetry**

Connect at least one source Superlog reads to find problems:

| Source | How it connects |
| - | - |
| OpenTelemetry | Paste a prompt into your coding agent. It adds Superlog as an exporter with a new ingest key. |
| [Sentry](https://docs.superlog.sh/integrations/sentry.md) | OAuth |
| [Datadog](https://docs.superlog.sh/integrations/datadog.md) | API key and application key |
| [Grafana](https://docs.superlog.sh/integrations/grafana.md) | OAuth for Grafana Cloud, or a service account token |
| [Axiom](https://docs.superlog.sh/integrations/axiom.md) | OAuth |
| [AWS CloudWatch](https://docs.superlog.sh/integrations/aws.md) | One CloudFormation stack |
| [Google Cloud](https://docs.superlog.sh/integrations/google-cloud.md) | Google sign-in |
| [Railway](https://docs.superlog.sh/integrations/railway.md) | OAuth |
| [Vercel](https://docs.superlog.sh/integrations/vercel.md) | Vercel integration |
| [PostHog](https://docs.superlog.sh/integrations/posthog.md) | OAuth |
| [Langfuse](https://docs.superlog.sh/integrations/langfuse.md) | Public and secret key |

Click a source to open its connect page. The OpenTelemetry page shows each service as data arrives.

**2. Connect GitHub and select repositories**

Click **Connect GitHub** and install the Superlog GitHub App. Then select the repositories Superlog may read to find the cause of a problem. Superlog never changes them.

You can skip this step. Without code, Superlog explains problems from telemetry alone.

**3. Connect Slack**

Connect your Slack workspace and choose the **Findings channel**. Every posted finding goes there. To post in a private channel, invite the Superlog app to it first.

**4. Add more context**

Connect [Linear](https://docs.superlog.sh/integrations/linear.md) so Superlog skips problems your team already tracks.

Turn on **Scan Slack to exclude known issues** and choose channels. Superlog then skips problems your team already discussed there.

This step is optional.

**5. Choose your plan**

Choose **Pro** or **Team** and pay in checkout. You need a findings channel first. Superlog turns on when checkout finishes and opens **Findings**. See [Plans and billing](https://docs.superlog.sh/settings/billing.md).

## After setup

* **Findings** lists every finding, with its severity and when it was found.
* **Usage** shows findings per day, and how many your team accepted.
* **Setup** holds the same settings in four sections: **General**, **Sources**, **Notifications**, and **Plan**. See [Finding settings](https://docs.superlog.sh/findings/settings.md).

Superlog posts a finding only when it confirms a problem. Until then, **Findings** is empty.

## Next steps

> [card] [How findings work](https://docs.superlog.sh/findings/how-it-works.md)
>
> What Superlog reads, reports, and skips.

> [card] [Finding settings](https://docs.superlog.sh/findings/settings.md)
>
> Minimum severity, daily limit, skipped services, and notes.


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