Integrations
Every tool Ace connects to, what Ace reads and can change in each, which ones open incidents, and how connecting a tool works.
Each integration has its own credential and permissions, and investigations only ever read. Ace changes something in a tool only when the credential allows it and an admin has turned on actions for that integration.
How integrations work
Admins connect integrations under Settings > Data sources, except Slack, which lives under Settings > Slack. Most tools take an API key or token. AWS uses a guided setup that creates a read-only IAM role, Kubernetes runs a connector as Deployments in your cluster, and GitHub and Slack use the Ace apps.
A workload is something you run, such as an API, a checkout flow or a background worker. An integration's alerts open incidents only on workloads that route it, so in the workload's settings, select the integration under Investigation triggers > Integration alerts.
Many tools send alerts by webhook. The integration's page in Ace shows the URL, and for some tools Ace adds the webhook itself. Ace polls some other tools every 2 minutes.
Investigation sources in the workload's settings sets which connected sources its investigations read. Once you save the list, Ace reads only those sources plus any source that routes the workload's alerts, so add any source you connect later. Until you save a list, the workload's alert sources decide what Ace reads. Code comes from the GitHub repositories linked to the workload.
Integrations that support actions show Allow Ace to run approved actions, and monitoring tools show Allow Ace to update this tool during incidents instead. Until an admin turns it on, Ace changes nothing in that tool. See Actions and approvals.
Disconnect on an integration's page removes the connection, and where it can, Ace also removes what it set up in the tool, such as its webhook. Afterwards, revoke the credential in the tool itself, using the steps on each integration's page.
Cloud and infrastructure
| Integration | Opens incidents | Ace can change |
|---|---|---|
| AWS | Yes, from CloudWatch alarms | Nothing with the read role. With the optional actions role, the services you choose, after approval |
| Kubernetes | Yes, from failing pods, rollouts and nodes | Nothing with the read connector. With a separate write connector, rollouts, scaling and more, after approval |
| Cloudflare | Yes, from Cloudflare notifications | Cache purge, Worker rollback, load balancer failover, security level, WAF rules, after approval |
Code and deploys
| Integration | Opens incidents | Ace can change |
|---|---|---|
| GitHub | No | Fix and revert pull requests, and your deploy workflow to roll back or redeploy |
| Vercel | Yes, from Vercel alerts. Deploys also join the change timeline | Rollback, promotion, redeploy and more, once actions are allowed |
Collaboration
| Integration | Opens incidents | Ace can change |
|---|---|---|
| Slack | Start an investigation with @Ace investigate <workload> | Posts in Slack. Nothing else |
Observability
| Integration | Opens incidents | Ace can change |
|---|---|---|
| Datadog | Yes, from monitor notifications | A downtime on the paging monitor during an approved fix, if allowed |
| Prometheus | Yes, from Alertmanager alerts | Nothing (read-only) |
| Grafana | Yes, from Grafana alerts | Annotations, and a silence on the paging rule during an approved fix |
| New Relic | Yes, from alert issues | A muting rule on the paging condition during an approved fix |
| Honeycomb | Yes, from triggers and SLO burn alerts | Markers when an incident opens and resolves |
| Elasticsearch | No | Nothing (read-only) |
| Axiom | Yes, from monitor alerts | Annotations when an incident opens and resolves |
| Logfire | No | Nothing (read-only) |
| Sentry | Yes, from Sentry alerts | Issue status and assignee, if allowed |
AI applications
| Integration | Opens incidents | Ace can change |
|---|---|---|
| LangSmith | No | Nothing (read-only) |
| LiteLLM | No. Read during investigations | Model fallbacks, budgets and rate limits, after approval |
Jobs and workflows
| Integration | Opens incidents | Ace can change |
|---|---|---|
| Trigger.dev | Yes, from failed production runs | Replay or cancel runs, pause or resume a queue, once actions are allowed |
| Inngest | Yes, from failed production runs | Rerun or cancel runs, pause or resume a function, once actions are allowed |
Databases
| Integration | Opens incidents | Ace can change |
|---|---|---|
| Supabase | Yes, from project health | Pooler size, read-only mode, disk size, restart. A person always approves |
| PlanetScale | No. Read during investigations | Deploy requests, and bounded backfills with a write password. A person always approves |
Product and feature flags
| Integration | Opens incidents | Ace can change |
|---|---|---|
| PostHog | Yes, from insight alerts | Feature flag rollout and on/off, once actions are allowed |
| LaunchDarkly | No. Changes join the change timeline | Flag on/off, rollout, restore an earlier version, once actions are allowed |
Paging and incident management
| Integration | Opens incidents | Ace can change |
|---|---|---|
| PagerDuty | Joins the open incident. A high-urgency page opens one if none is open | Nothing in your incidents (read-only) |
| incident.io | Joins the open incident, or opens one if none is open | Nothing (read-only) |
Don't see your tool?
Tell us which tool you use and what Ace would need to read from it: talk to our team.
Next steps
- Quickstart: connect your first integrations and run an investigation.
- How Ace works: how alerts from these tools become one incident.
- Security and data: what each credential can reach.
Operating rules
Write plain-language rules that tell Ace how your team wants incidents diagnosed and fixed, and understand exactly where Ace applies them and what they can't do.
AWS
Connect AWS so Ace can read CloudWatch, CloudTrail, X-Ray and your infrastructure during investigations, open incidents from CloudWatch alarms, scan for savings and, if you allow it, make approved changes.