Add Incident Impacts
FireHydrant allows you to add impact infrastructure to your incident automatically through a runbook step.
In the step you can add any combination of Services, Environments, and Functionalities to your incident and specify the impact condition that you'd like these to be attached with.
This can be helpful for automatically adding a consistent set of functionalities to every incident, or programatically adding services to an incident when specific conditions are met.
Example Use Cases
- Adding a Functionality or Environment when a specific Service is impacted
- For example, if you initiate an incident with a known Service that's impacted, you may want to mark the upstream Functionality or Environment it's tied to as
Degradedor some other condition.
- For example, if you initiate an incident with a known Service that's impacted, you may want to mark the upstream Functionality or Environment it's tied to as
- Add multiple Services, Functionalities, or Environments when a specific tag is added to the incident
- Maybe you have certain types of incidents that you track via tags. Aside from using our incident types, you could also automate using this step.
- For example, "If incident is tagged
full-ui" then add "User Portal", "Admin Portal" functionalities, and "app-cdn" and "app-fe" services.