Automatically sending alerts via Services
FireHydrant’s Service alerting feature automatically pages the escalation policy for a particular service when it is added to a new incident. This enables engineers to focus on remediation while knowing that the right members of service teams are being notified about an incident.
Follow the below steps to activate this feature.
Configuring Auto-Alerts for Services
1. Confirm the Integration is installed on FireHydrant
This feature is currently supported for the following integrations: PagerDuty, Opsgenie, and VictorOps. After one of these integrations is installed, you will have the ability to link services in the alerting provider with services in FireHydrant.
To learn more about installing integrations, see the corresponding docs pages under Integration Guides on the left for the above supported alerting providers.
2. Confirm the service(s) in your alerting provider are linked with service(s) in FireHydrant.
- In the FireHydrant left nav, click Service Catalog , then Services.
- Click into the service you would like to have Auto-Alerting turned on for and make sure an Integration Link for PagerDuty, Opsgenie, or VictorOps exists. For details on Integration Links , see Linking services in other tools to FireHydrant services.
- Alternatively, you can directly import services from your alerting provider to FireHydrant, and this will also automatically create the link between them.
3. Turn on Automatic Alerting
- On the page for each service you'd like to Auto-Alert, click Edit details in the top right corner.
- Scroll down to the "Alerting" section.
- Check box for "Automatically alert if added to an incident", and then Save edits.
4. Using Auto-Alerting
To automatically page the service, all you need to do now is mark a service as impacted in an incident. This can occur both during an ongoing incident as well as when first declaring the incident.
FireHydrant will send out the request to PagerDuty via the linked service, and which ever Escalation Policy is assigned as the default for that service will be paged. The FireHydrant Incident Timeline also reflects that an alert was generated via that service.