---
title: "Integrations overview"
description: "Connect observability, cloud, data, and messaging tools for automated RCA"
---

OpenSRE investigates alerts by querying the same tools your engineers use. Connect your stack so OpenSRE can pull logs, check recent deploys, map dependencies, and deliver findings where your team already works.

## Two setup paths

| Path | Best for | How to configure |
| --- | --- | --- |
| **Local CLI** | Self-hosted `opensre` on your laptop or server | `opensre onboard` or `opensre integrations setup`, plus env vars |
| **Hosted (OpenSRE Cloud)** | Org-wide connectors shared across users | [app.tracer.cloud](https://app.tracer.cloud) web app |

Most users start with the **local CLI** path. You need credentials for the tools you want to connect and permission to create API keys.

## Local CLI setup

```bash
opensre integrations setup
```

Or set environment variables — OpenSRE picks them up automatically on the next run.

### Verify

```bash
opensre integrations verify
opensre integrations verify datadog
```

Inside the interactive shell you can also run `/integrations list`, `/integrations verify <name>`, `/verify`, and `/health`.

## Integration catalog

| Category | Integrations |
| --- | --- |
| **Observability and incidents** | [Alertmanager](/alertmanager), [Azure Monitor](/azure-monitor), [Better Stack](/betterstack), [Coralogix](/coralogix), [Datadog](/datadog), [Grafana](/grafana), [Hermes](/hermes), [Honeycomb](/honeycomb), [Incident.io](/incident_io), [OpenObserve](/openobserve), [OpsGenie](/opsgenie), [Sentry](/sentry), [SignOz](/signoz), [Splunk](/splunk), [Victoria Logs](/victoria_logs) |
| **Cloud and infrastructure** | [AWS](/aws), [Argo CD](/argocd), [Helm](/helm), [Jenkins](/jenkins), [Vercel](/vercel) |
| **Databases and data platforms** | [Azure SQL](/azure-sql), [ClickHouse](/clickhouse), [Kafka](/kafka), [MariaDB](/mariadb), [MongoDB](/mongodb), [MongoDB Atlas](/mongodb-atlas), [MySQL](/mysql), [OpenSearch](/opensearch), [PostgreSQL](/postgresql), [RabbitMQ](/rabbitmq), [RDS](/rds), [Snowflake](/snowflake), [Supabase](/supabase) |
| **Source control and collaboration** | [Bitbucket](/bitbucket), [GitHub](/github), [GitHub Actions](/integrations/github-actions), [GitLab](/gitlab), [Google Docs](/google-docs), [Jira](/jira), [Trello](/integrations/trello) |
| **Workflow orchestration** | [Airflow](/airflow), [Dagster](/dagster), [Prefect](/prefect), [Temporal](/temporal) |
| **Messaging** | [Slack](/messaging/slack), [Discord](/messaging/discord), [Telegram](/messaging/telegram), [WhatsApp](/messaging/whatsapp), [Twilio SMS](/messaging/twilio-sms) |
| **AI coding assistants** | [OpenClaw](/openclaw) |

[Multi-instance integrations](/multi-instance-integrations) let you register multiple clusters, regions, or accounts per provider (for example prod and staging Grafana).

## Hosted (OpenSRE Cloud) setup

Enterprise connectors are configured through the OpenSRE web app at [app.tracer.cloud](https://app.tracer.cloud). Once connected, they are available to all users in your organization.

**Observability.** Connect [Grafana](/grafana) and [Datadog](/datadog) for logs, metrics, traces, and alerts.

**Infrastructure.** Connect [AWS](/aws) to map your environment across clouds and clusters.

**Communication.** Deliver investigation reports via [Slack, Discord, or Telegram](/messaging/index).

<Frame>
  ![Integrations](/images/integrations.png)
</Frame>

### Example: Datadog in the web app

1. **Name** — distinguish between instances (for example `prod` vs `staging`)
2. **API key** — create in Datadog and paste into OpenSRE
3. **Application key** — create in Datadog and paste into OpenSRE

<Frame>
  ![Connect Datadog](/images/connect_datadog.png)
</Frame>
