Using alerting schedules to assign roles

If you use an alerting provider, FireHydrant can integrate and directly pull people from your escalation policies and on-call schedules.

Prerequisites

Currently, FireHydrant supports the following providers:

• PagerDuty
• Opsgenie
• Splunk On-Call (VictorOps)

Make sure you have one of these providers set up and configured for your FireHydrant account.

Set on-call schedules in FireHydrant Teams

1. Navigate to Settings > Teams.
2. From here, you can click either Add a team to create a new team, or find the team you'd like to edit from the list of teams, click into it, then Edit.
3. In the Memberships section of the page, click on the Member name dropdown. Along with the users from your FireHydrant organization, you will also see your PagerDuty, Opsgenie, or Splunk On-Call (VictorOps) schedules.
   • When you select an on-call schedule as a member, the person who is on-call for that schedule at the time of the Team's assignment to an incident will be the user brought in to said incident.

4. Under Role, select a role to assign this on-call user to.
5. Make other changes to the team as needed, and click Create team or Save changes.

Other Important Notes

• The user that is on-call must also have an account in FireHydrant and their email addresses between the apps must match in order for FireHydrant to pull them into the incident channel.
• Changes, such as deletions or additions of on-call schedules or escalation policies, aren't automatically detected by FireHydrant. If, for example, you add a new on-call schedule to your alerting provider, you will need to go to the integration settings for said alerting provider and click Refresh Schedules before that new schedule shows as an option in the dropdown in other parts of FireHydrant (like Teams configuration).

Pulling in on-call responders

Once you've completed the above steps, FireHydrant will automatically pull in whoever is on-call when the Team is assigned to an incident. This will work regardless of whether the team was manually assigned or automatically as part of Runbooks or Service Catalog settings.