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

# Integrations

> Everything Ordyn connects to. Connect from the Connections page in the app.

Ordyn works inside the tools you already have. Connect them from **Connections** in the app. Access to observability tools and databases is read-only. Auto Monitors needs extra permission to create monitors, and each provider's page lists every permission Ordyn uses.

## Required

| Integration | Why |
| - | - |
| [GitHub](/integrations/github) | Read code, review pull requests, open fixes. Auto Monitors works on your default repository. |
| [Slack](/integrations/slack) | Deliver alerts and investigations. Take requests in threads. |

## Work tracking

| Integration | What it adds |
| - | - |
| [Linear](/integrations/linear) | Investigate issues on assignment or mention. Auto-investigate new issues in a team. |
| [Jira](/integrations/jira) | Same for Jira Cloud projects. |
| [Asana](/integrations/asana) | Same for Asana projects. |

## Logs, metrics, and alerting

| Integration | What Ordyn reads | Auto Monitors can create monitors here |
| - | - | - |
| [Sentry](/integrations/sentry) | Stack traces, breadcrumbs, error frequency, affected users | Yes |
| [Datadog](/integrations/datadog) | Metrics, monitors, APM traces, logs, events | Yes |
| [Grafana](/integrations/grafana) | Alert rules, plus metrics, logs, and traces through its data sources | Yes |
| [AWS CloudWatch](/integrations/aws-cloudwatch) | Log groups, Logs Insights queries, metrics | Yes |
| [Azure Monitor](/integrations/azure-monitor) | Log Analytics workspaces, KQL queries | Yes |
| [Google Cloud](/integrations/google-cloud) | Cloud Logging entries and log-based queries | Yes |
| [Prometheus](/integrations/prometheus) | PromQL metrics and alerting rules | No |
| [Loki](/integrations/loki) | Log streams by label | No |
| [Axiom](/integrations/axiom) | Logs and events | No |
| [BetterStack](/integrations/betterstack) | Logs | No |
| [Mezmo](/integrations/mezmo) | Logs | No |
| [SumoLogic](/integrations/sumologic) | Log search | No |
| [Render](/integrations/render) | Service logs and deploy events | No |
| [Kubernetes](/integrations/kubernetes) | Pod logs, events, pod status | No |

## Databases

Read-only SQL for data questions and impact measurement.

| Integration | Notes |
| - | - |
| [PostgreSQL](/integrations/postgresql) | Direct or through an [SSH tunnel](/integrations/ssh-tunnels) |
| [PlanetScale](/integrations/planetscale) | Postgres through an [SSH tunnel](/integrations/ssh-tunnels) supported |
| [BigQuery](/integrations/bigquery) | |
| [Snowflake](/integrations/snowflake) | Key-pair auth, event tables, query history |

## Your own tools

| Integration | What it adds |
| - | - |
| [Custom MCP connectors](/integrations/custom-mcp) | Connect internal tools that expose a remote MCP server. |

## Coding agents

Ordyn can hand fixes to [Cursor or Devin](/fix/overview) instead of its own build agent. You can also bring any investigation into [Claude Code or Cursor](/fix/overview#hand-off-to-your-coding-agent) through the Ordyn MCP server.

> [!NOTE]
>
> Need something not listed? New integrations usually take days, not months. Email [help@ordyn.dev](mailto:help@ordyn.dev).


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