An overview of integrations

FireHydrant Full-Cycle Incident Management
FireHydrant Full-Cycle Incident Management

FireHydrant centralizes your incident management processes by integrating with the tools you already use. This article is a high-level overview of the types of integrations we offer and what you can do with them. For help setting up specific integrations, reference our integration guides on the left under Integration Guides.

Alerting integrations

FireHydrant integrates with alerting tools like PagerDuty, Opsgenie, and Splunk On-Call (VictorOps), to unlock the following features:

  • Kick-off your incident response process directly from an alert in Slack
  • Import services from your alerting tool into FireHydrant's service catalog
  • Sync on-call schedules so anyone can see who's on call by running a command in Slack
  • Page your team members

Reference our alerting integration docs on the left under Integration Guides > Alerting to learn more.

Monitoring integrations

On top of alerting tools, FireHydrant also supports direct integrations with a number of monitoring providers so that any issues or alerts raised in those tools can automatically kick off incidents in Firehydrant. These providers include:

Along with the alerting tools, these integrations support Alert Routing, where FireHydrant can flexibly decide to route certain alerts into different Slack channels for manual triaging, or automatically opening incidents based no a variety of conditions.

Ticketing integrations

FireHydrant integrates with ticketing tools, like Jira and Zendesk, to enable the following functionality:

  • Automatically create an incident ticket when you declare an incident in FireHydrant
  • Capture follow-up tasks as Jira tickets during a retrospective
  • Link Zendesk tickets to an incident to capture impacted customers
  • Pass incident status updates from FireHydrant to Zendesk

Reference our ticketing integration docs on the left under Integration Guides > Ticketing to learn more.

Messaging integrations

FireHydrant integrates with Slack so you can declare and respond to incidents where your team is already collaborating. The Slack integration allows you to do the following:

  • Declare incidents to kick-off your Runbook(s)
  • Assign roles and teams to an incident
  • See who is on-call
  • Add notes to incidents
  • Easily capture important messages in your retrospective by "starring" them
  • Page a team member
  • Resolve incidents
  • And much more

FireHydrant also has a rudimentary Microsoft Teams integration, however it is not feature-par with the Slack integration and is only capable of notifications to channels.

Reference our messaging integration docs on the left under Integration Guides > Messaging to learn more.

Video conferencing integrations

FireHydrant integrates with video conferencing tools, like Zoom, Google Meet, and Cisco Webex, to support the following functionality:

  • Automatically create a video conference call when you declare an incident
  • Configure whether you want the call to be recorded by default
  • Use template variables to dynamically name the meeting topic and meeting agenda (for example using the incident severity, incident name, and incident description).

Reference our video conferencing integration docs on the left under Integration Guides > Video Conference to learn more.

Other integrations

FireHydrant integrates with other tools as well, for example change event streams and external status pages. Here are some of the other things you can do with our integrations:

  • Publish incidents to Atlassian Statuspage
  • Export retrospective data into collaborative document management tools, like Google Docs and Confluence
  • Import services and change events from GitHub
  • Use Kubernetes to automatically send updates about the workloads deployed in your clusters to FireHydrant
  • Turn failed checks from Checkly into alerts which then turn into incidents on FireHydrant
  • Ingest change events from AWS CloudTrail
  • Manage your FireHydrant configuration and account with Terraform

Reference our other integration docs on the left under Integration Guides > Other to learn more.

Last updated on 2/9/2024