Using alerting schedules to assign roles

If you use an alerting provider, it's important to integrate your schedules from that provider with FireHydrant. This way the proper on-call responders are dynamically added to an incident; you don't have to add them from a static user list.

With FireHydrant's PagerDuty, Opsgenie, and Splunk On-Call (VictorOps) integrations, you can sync on-call schedules with your FireHydrant teams, so team assignments in FireHydrant are always dictating your current on-call rotation. After setting up integration with your alerting provider, you can start assigning on-call schedules.

To get started:

  1. In the left nav, click Incident Response > Teams.
  2. From the list of team names, find the team where you want to add the on-call role and click Edit in the upper-right corner of the page.  
  3. Edit the team where you want the on-call role to be assigned. In the Members section of the page, you can assign a user to a specific role.
    editing_team_member.png
    Along with the users from your FireHydrant organization, you will also see your PagerDuty, Opsgenie, or Splunk On-Call (VictorOps) schedules. When selecting a schedule to be assigned to a given role, the person who is actively on-call for that schedule will be the user brought in to an incident in FireHydrant when the respective team is pulled in.

There are four important things to note:

  • The user within the on-call schedule in the alerting provider must also be a user inside of FireHydrant.
  • FireHydrant gets user information by email, so the user email addresses from both tools must match to sync correctly.
  • A user's account in FireHydrant must be linked with their Slack account. (Users whose accounts are not already linked can link them by running /fh link in Slack).
  • If your schedules are incorrect when assigning a role, you may need to manually refresh schedule data from your alerting provider. You can do so by going to the integration settings for your alerting provider and clicking Refresh Schedules.
    refresh.schedules.png

 

 

Last updated on 3/28/2023