In this tutorial, we'll go over how to declare an incident on FireHydrant through an alert on PagerDuty, Opsgenie, or Victorops. As a preface, you must have both the alerting and Slack integrations configured.
Using our alerting and Slack integrations, you'll be able to receive alerts on Slack whenever an incident is created on your alerting tool. From here, you'll have the option to declare a new incident on FireHydrant through Slack. This will, in parallel, link the respective alert to the newly created incident on FireHydrant.
To do this, head over to your integrations page. Under "Slack", select "Configure Integration".
From here, you'll have the option to select which Slack channel you'd like to notify in the event that an incident is created on PagerDuty. In the example below, I am notifying my #staging-alerts channel in Slack.
Now, whenever an incident is created on your Alerting tool, FireHydrant's slack bot will message the Slack channel configured above. The slack bot will ask if you'd like to declare an incident on FireHydrant, link the alert to an existing incident, or ignore the alert entirely.
When you select "Open Incident", FireHydrant will automatically assign the alert as the primary alert for the incident, meaning if the incident is resolved on your alerting tool, the incident would automatically be resolved on FireHydrant. You'll have the option to prevent this sync from happening by visiting the incident Command Center External Resources Linked Alerts, and unchecking the "Primary Alert" box.
If you have already linked and imported your services from PagerDuty or Opsgenie into FireHydrant, the service impacted in PagerDuty or Opsgenie will auto assign that service as impacted within FireHydrant.