Incident Tags

This article describes how to use incident tags and how to add them to an incident.

Creating tags enables you to trigger a Runbook based on a tag. You can also use tags to store easily-queried metadata about incidents, which you can use later as search criteria. Some tag types include:

  • Code causes
  • Customer impact conditions
  • Types of incidents

Creating tags

You can create a new tag by:

  • Typing a new tag name on the declare incident form. This works in Slack or the web UI.
  • Typing a new tag name while editing your incident. This works in Slack or the web UI.
  • Running the /fh tags or /fh add tags commands in an active incident channel in Slack and typing the tag name.
Adding a new tag via Slack
Adding a new tag via Slack

Adding tags to an incident

You can add tags to an incident by:

  • Creating an incident through the new incident page, where you can add existing and new tags
  • Creating an incident through an incident type, where you can create a type with existing and new tags
  • Creating an incident through the Slack new incident modal, where you can add new and existing tags
  • Editing an incident through the FireHydrant web app
  • Running the /fh tags or /fh add tags command in an active incident channel in Slack
  • Via API

Using Tags

Filtering

Once you've tagged some incidents, you'll be able to filter by tags on both the Incidents page as well as on the Analytics page.

Filtering analytics by tags
Filtering analytics by tags

Automation through tags

Tags also work as Runbook conditions. You can kick off individual Runbook steps, or attach new Runbooks to an incident with tags. To learn more, see this article on automating your workflow using Runbook conditions..

Last updated on 9/29/2023