Set Up Integration Management
Harness AI SRE connects to the tools you already use across monitoring, CI/CD, ticketing, communication, and on-call. Each integration feeds AI SRE the signals it needs to detect, investigate, and resolve incidents, or lets AI SRE act on those tools during a response.
How AI SRE integrates with external tools
AI SRE supports external technologies through four mechanisms. A single technology can use more than one.
- Alert webhooks: Monitoring and observability tools POST alerts to an AI SRE webhook URL, which creates or updates incidents. Go to Set Up Alert Management to configure webhooks.
- Change sources: CI/CD tools and source control send build, deploy, and pull request data to the Deploy Change Investigator for incident correlation. Go to Configure Sources of Change to configure change sources.
- Runbook actions: Runbooks call out to communication, ticketing, and incident-management tools to automate response. Go to Set Up Runbook Management to configure runbook actions.
- On-call sync: On-call tools synchronize their schedules and escalation policies into AI SRE. Go to Set Up On-Call Management to configure on-call sync.
Most connector-based integrations are configured under Project Settings or Organization Settings → Third Party Integrations (AI SRE). Webhook-based integrations use a webhook URL and require no connector.
Monitoring and observability
Ingest alerts from monitoring and observability tools to create and enrich incidents.
- Datadog: Ingest Datadog monitor alerts through a webhook.
- New Relic: Ingest New Relic alert conditions through a webhook.
- Splunk: Ingest Splunk alerts through a webhook.
- Dynatrace: Ingest Dynatrace problem notifications through a webhook.
- Grafana: Ingest Grafana alerts through a webhook.
- Prometheus: Ingest Prometheus Alertmanager alerts through a webhook.
- AWS CloudWatch: Ingest CloudWatch alarms through an SNS webhook.
- Sentry: Ingest Sentry issue alerts through a webhook.
- AlertSite: Ingest AlertSite monitoring alerts through a webhook.
- BigPanda: Ingest BigPanda alerts through a webhook.
- Lacework: Ingest Lacework security alerts through a webhook.
- Harness SLO: Ingest Harness Service Reliability Management SLO alerts.
CI/CD and change sources
Track builds, deployments, and code changes to correlate them with incidents.
- GitHub: Ingest pull requests and send build and deploy webhooks.
- GitLab: Send build and deploy webhooks from GitLab CI/CD.
- Bitbucket: Ingest pull requests from Bitbucket Cloud.
- Jenkins: Send build and deploy webhooks from Jenkins pipelines.
- CircleCI: Send build and deploy webhooks from CircleCI workflows.
- Travis CI: Send build and deploy webhooks from Travis CI.
- Octopus Deploy: Send deployment webhooks from Octopus Deploy.
- Terraform: Send Terraform apply events as deployment data.
- Harness Code: Ingest pull requests automatically, with no connector required.
- Harness Pipelines: Send build and deploy data, and trigger pipelines from runbooks.
Ticketing and ITSM
Track change records and automate ticket actions during incidents.
- Jira: Track Jira deployments and automate Jira ticket actions.
- ServiceNow: Ingest ServiceNow change records and automate ticket actions.
- Jira Service Management: Create Jira Service Management alerts from runbooks.
- Confluence: Create and update Confluence pages from runbooks.
Communication
Collaborate on incidents and send notifications through chat platforms.
- Slack: Collaborate on incidents and run Slack commands.
- Microsoft Teams: Collaborate on incidents and post messages.
- Google Chat: Collaborate on incidents in Google Chat spaces.
- Zoom: Create meetings and conference bridges from runbooks.
On-call and escalation
Synchronize on-call schedules and page responders.
- PagerDuty: Synchronize on-call schedules and create incidents.
- OpsGenie: Synchronize on-call schedules and create alerts.
- xMatters: Synchronize on-call schedules.
Custom integrations
- Custom webhooks: Ingest alerts from any tool that can send an HTTP POST, using a custom webhook template with CEL or Mustache field mapping.