FireHydrant centralizes your incident management processes by integrating with the tools you already use. This article is a high-level overview of our integrations and what you can do with them. For help setting up specific integrations, reference our integration guides within the article below or on the left under their respective sections.
- Kick off your incident response process directly from an alert
- Import services from your alerting tool into FireHydrant's Service Catalog
- Connect on-call schedules so responders can look up and page on-call personnel
- Automatically paging service owners when services are impacted on incidents
- ...and more!
To learn more, reference our alerting integration docs on the left under Integrations > Alerting & Monitoring. In addition, Alerting Integrations support Alert Routing, which lets you define when inbound alerts should automatically create incidents and based on what parameters.
On top of alerting tools, FireHydrant also supports direct integrations with several monitoring providers so that any alerts raised in those platforms can automatically kick off incidents in FireHydrant. Those providers include:
Like the alerting tools, these integrations also support Alert Routing.
FireHydrant integrates with Slack so you can declare and respond to incidents where your team is already collaborating. The Slack integration allows you to conduct entire incidents end-to-end, including:
- Declaring incidents and kicking off Runbook automation
- Assigning roles and teams to an incident
- Seeing who is on-call and paging teams and people
- Adding notes to incidents
- Capturing key messages and all events in the incident timeline
- Resolving incidents
- ...and more
FireHydrant also has a rudimentary Microsoft Teams integration to start incidents and notify channels. Refer to our messaging integration docs on the left under Integrations > Messaging to learn more.
- Automatically creating FireHydrant incidents from new tickets in the external tool
- Automatically create a ticket in the external tool when you declare an incident in FireHydrant
- Capturing follow-ups as tickets in the external tool and linking those to the original incident ticket
- ...and more
Refer to our ticketing integration docs under Integrations > Ticketing to learn more.
- Automatically create a conference bridge when you declare an incident
- Configure whether you want the call to be recorded (applies only to certain integrations)
- Use template variables to dynamically name the meeting topic and agenda (for example, using the incident severity, incident name, and incident description)
Refer to our video conferencing integration docs on the left under Integrations > Video Conferencing to learn more.
FireHydrant integrates with other tools, such as change event streams and external status pages. Here are some of the different integrations you can configure on FireHydrant:
- Publish incidents to Atlassian Statuspage
- Export retrospective data into collaborative document management tools, like Google Docs and Confluence Cloud
- Import services and change events from GitHub
- Use Kubernetes to automatically ingest change events and catalog services deployed in your clusters to FireHydrant
- Turn failed checks from Checkly into alerts or incidents on FireHydrant
- Ingest change events from AWS CloudTrail
- Manage your FireHydrant configuration and account with Terraform
- Link Zendesk tickets to incidents to track customer impact and automatically post incident updates to those tickets as internal notes
Reference our other integration docs on the left under Integrations > Other to learn more.
Updated about 2 months ago