On-Call Paging and Lookup
FireHydrant allows you to directly page teams as well as look up who's on call for any given Service or Functionality.
Prerequisites
- You need to have configured an alerting provider. The providers we support are:
- Signals (FireHydrant native alerting/on-call)
- Opsgenie
- PagerDuty
- Splunk On-Call (VictorOps)
- If you want to page Services, Functionalities, or Environments, you'll first need to link them with external services/schedules.
Paging users, teams, and escalation policies
via User Interface (Signals only)
You can page users/teams from anywhere within FireHydrant by clicking on "Send Alert" at the top header bar. When you page from the UI, you can choose to target Escalation Policies, On-Call Schedules, Teams, or Users.
Note that any targets missing required settings or configurations will be marked with a small warning triangle ⚠️ and an indicator will be shown in the UI.
via Slack
For any of the 3rd party alerting providers that FireHydrant supports, you can easily page any user, team, escalation policy, or service (depending on which alerting provider you use). The command is:
/fh page # Opens up the general paging modal
/fh page
opens the general paging modal, which allows you to choose your provider (if multiple are configured) and directly choose other details like who/what to page.
If you want to add additional users, teams, or escalation policies to a page or alert that has already been connected to an incident, you can select that page/alert from the "Select or create a page" dropdown.
You can craft a quick message and longer description for your page, and FireHydrant will also add a link to the Slack channel when sending the page through your alerting provider.
Each provider will have slightly different requirements around fields, services, and who to page.
Provider | Required Fields | Optional Fields |
---|---|---|
Signals | - Summary - Who should be paged? | - Description |
PagerDuty | - Message - Affected Services | - Description - Who should be paged? |
Opsgenie | - Message | - Incident Priority - Affected Services - Who should be paged? |
Splunk On-Call | - Message - Who should be paged? | - Description |
Once a page has been sent, FireHydrant will post a message in the channel that will track the status of the page, and a link to the page will be included in the incident's list of external links.
Paging specific component owners
Note:
As of today, you can't page specific component's owners if you're using FireHydrant's Signals. You'll need to use
/fh page
above and page the team(s) directly.
In addition to paging a user or team directly, you can page a team that is linked to a service or functionality. To page a team this way, you can run:
/fh page service [slug] # Page a specific service's on-call responders
/fh page functionality [slug] # Page a specific functionality's on-call responders
Lookup who's on-call for specific components
Note:
As of today, you can't look up on-call for specific components if you're using FireHydrant's Signals. You'll need to use
/fh signals-on-call
and check the team(s) directly.
Directly from Slack, you can run /fh oncall
or /fh on-call
. This will pop up a contextual message asking which Service or Functionality you'd like to see the on-call information for.
Selecting the Service or Functionality will return the information your alerting provider gave to FireHydrant.
If you're using FireHydrant's Signals, you can use the /fh signals-on-call
to look up who is on-call for your teams or teams across the entire company.
Next Steps
- See the Integrations Overview for more information about our alerting integrations
- See Slack Commands for the full list of available Slack commands
- Continue on to Managing Tasks
Updated 3 months ago