# Ordyn

- [What's Ordyn](/docs/index.md): Ordyn is the AI production engineer. It watches every change you ship, keeps your alerting tuned, and fixes production when it breaks.
- [Quickstart](/docs/quickstart.md): Connect your stack, turn on Auto Monitors, and see your first monitored change.
- [Shadow mode](/docs/shadow-mode.md): Run Ordyn silently next to your real alert channel before you change anything.
- [Auto Monitors](/docs/detect/overview.md): Monitors that create themselves from your pull requests and stay tuned as production changes.
- [Set up Auto Monitors](/docs/detect/setup.md): A few decisions, then Ordyn does the rest on your next pull request.
- [Pull requests](/docs/detect/pull-requests.md): What Ordyn posts on each pull request and how to control it.
- [Deploys](/docs/detect/deploys.md): Tell Ordyn when a change reaches production. Ordyn creates the monitors and confirms the deploy is healthy.
- [Keeping monitors tuned](/docs/detect/maintenance.md): Monitors rot when nothing owns the upkeep. Ordyn owns it.
- [How triage works](/docs/triage/overview.md): Every alert is investigated and graded before it reaches Slack. Only real impact gets through.
- [Investigations](/docs/triage/investigations.md): What an investigation contains and how to read it.
- [Alert sources](/docs/triage/alert-sources.md): Have Ordyn investigate the alerts and issues you already get, from Slack, Linear, Jira, and Asana.
- [Sensitivity and routing](/docs/triage/sensitivity-and-routing.md): Decide which Slack channel each alert goes to and how much each channel should hear.
- [Incident channels](/docs/triage/incident-channels.md): Ordyn joins the channel when an incident is declared and starts investigating from what your team posts.
- [Fix with Ordyn](/docs/fix/overview.md): Ordyn writes the fix and opens the pull request, or hands the work to your own coding agent. You review and merge.
- [Open Issues](/docs/open-issues/overview.md): One view of what is actually broken right now, tracked from open to verified resolution.
- [Working with Ordyn in Slack](/docs/slack/overview.md): What an alert looks like, how to ask follow-ups, and how to change monitoring from the thread.
- [Investigate on demand](/docs/slack/investigate-on-demand.md): Ask Ordyn about your alerts, logs, metrics, or code any time, from Slack, the app, or your issue tracker.
- [Memories](/docs/agent/memories.md): What Ordyn remembers about your systems between investigations.
- [Skills](/docs/agent/skills.md): Procedures Ordyn follows when the symptoms match.
- [Automations](/docs/agent/automations.md): Run an agent on a schedule: status reports, on-call handoffs, noise reviews.
- [Workspace and billing](/docs/account/settings.md): Manage your workspace, keys, usage, and plan.
- [MCP server](/docs/reference/mcp-server.md): Tools your coding agent can call once the Ordyn MCP server is installed.
- [Ordyn CLI](/docs/reference/cli.md): Sign in to Ordyn, manage workspaces, connect your coding agent and set up Auto Monitors from the terminal.
- [Deployments API](/docs/reference/deployments-api.md): Tell Ordyn that a SHA reached an environment when your pipeline does not create GitHub Deployments.
- [Security](/docs/reference/security.md): How Ordyn handles access and data.
- [Permission changes](/docs/reference/permission-changes.md): Every change to what Ordyn asks for in your tools, newest first.
- [Troubleshooting](/docs/help/troubleshooting.md): Fixes for the most common setup problems.
- [FAQ](/docs/help/faq.md): Straight answers to the questions we hear most.
- [Integrations](/docs/integrations/overview.md): Everything Ordyn connects to. Connect from the Connections page in the app.
- [GitHub](/docs/integrations/github.md): Required. How Ordyn reads your code, reviews pull requests, and opens fixes.
- [Slack](/docs/integrations/slack.md): Where alerts, investigations, and requests happen.
- [Linear](/docs/integrations/linear.md): Investigate issues on assignment or mention, or auto-investigate new issues in a team.
- [Jira](/docs/integrations/jira.md): Investigate Jira Cloud issues on assignment or mention, or auto-investigate new issues in a project.
- [Asana](/docs/integrations/asana.md): Investigate Asana tasks on assignment or mention, or auto-investigate new tasks in a project.
- [Sentry](/docs/integrations/sentry.md): Error details for investigations. Auto Monitors can create Sentry alerts and receive them.
- [Datadog](/docs/integrations/datadog.md): Metrics, monitors, traces, and logs for investigations. Auto Monitors can create Datadog monitors.
- [Grafana](/docs/integrations/grafana.md): Query Grafana data sources and alerts. Auto Monitors can create Grafana alert rules.
- [AWS CloudWatch](/docs/integrations/aws-cloudwatch.md): Read CloudWatch logs and metrics through an IAM role. Auto Monitors can create CloudWatch alarms.
- [Azure Monitor](/docs/integrations/azure-monitor.md): Read Log Analytics, native metrics and Managed Prometheus through an app registration. Auto Monitors can create Azure alert rules and Prometheus rule groups.
- [Google Cloud](/docs/integrations/google-cloud.md): Read Cloud Logging and Cloud Monitoring through a service account. Auto Monitors can create alert policies.
- [Prometheus](/docs/integrations/prometheus.md): Query metrics and alerting rules from any PromQL-compatible endpoint.
- [Loki](/docs/integrations/loki.md): Query log streams from Grafana Cloud or self-hosted Loki.
- [Axiom](/docs/integrations/axiom.md): Query logs and events in Axiom.
- [BetterStack](/docs/integrations/betterstack.md): Query logs in BetterStack.
- [Mezmo](/docs/integrations/mezmo.md): Query logs in Mezmo.
- [SumoLogic](/docs/integrations/sumologic.md): Run log searches in SumoLogic.
- [Render](/docs/integrations/render.md): Read service logs and deploy events from Render.
- [Kubernetes](/docs/integrations/kubernetes.md): Read pod logs, events, and pod status directly from your cluster.
- [PostgreSQL](/docs/integrations/postgresql.md): Read-only SQL against your Postgres database during investigations and for measuring impact.
- [PlanetScale](/docs/integrations/planetscale.md): Read-only SQL against your PlanetScale database.
- [SSH tunnels](/docs/integrations/ssh-tunnels.md): Connect Ordyn to a database that isn't reachable from the internet, through a bastion host.
- [BigQuery](/docs/integrations/bigquery.md): Read-only SQL against BigQuery.
- [Snowflake](/docs/integrations/snowflake.md): Read-only SQL, query history, and event-table telemetry through key-pair auth.
- [Custom MCP connectors](/docs/integrations/custom-mcp.md): Give Ordyn's agents access to your own tools through remote MCP servers.


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