Impacted Components

FireHydrant's Service Catalog is a critical platform feature that helps you conduct better incidents. By tracking which parts of your infrastructure/application are impacted, as well as assigning owning users and teams, you can unlock capabilities like:

• Tracking Impact Statistics by components, users, teams, and more
• Automatically adding the right teams for a particular component as well as alerting/paging them on an incident
• Associating recent changes with incidents to give responders a head start on what to investigate

Depending on how your organization has configured Incident Fields, impacted Environments, Functionalities, and Services are fields you should be able to set when declaring and at any point throughout the incident.

Adding impacted components via Slack

In Slack, you can set affected components using a few commands:

• /fh new - You can set impacted components when declaring the incident (unless your admins have hidden these fields)
• /fh update - You select components when posting incident updates. This allows you to change the incident's milestone, change impacted components, and post updates to a status page in one swift motion. This command can be run at any point through the incident and even through Retrospective if the incident channel still exists.

Once you've added components during an incident, FireHydrant will also surface the related Teams, Services, Functionalities, or other items for you to take action:

Adding impacted components via Command Center

You can add impacted components in the user interface by scrolling down to the Impacts section of the details panel on the right side. Clicking the edit pencil will open a modal to select items from the Catalog.

Adding impacted components via integrations

Some integrations allow you to select impacted components when declaring an incident via the external application:

• The Zendesk integration allows you to choose Functionalities and any custom fields when declaring from the Zendesk support portal.