Incident Tags

This article describes how you can use incident tags and how to add them to an incident.
Tags let you store easily-queried metadata for your incidents. Some types include:
  • Cause codes
  • Customer impact conditions
  • Types of incidents

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 you can add new and existing tags
  • Editing an incident through the FireHydrant web app
  • Running the /fh tags command in an active incident channel in Slack

Querying by tags

Currently, you can query incidents by tags in both the API and on the incidents list.


When you add a tag to an incident, it becomes available to query on the incident filter page. After you have selected one or more tags, you have the option to select a tag matching strategy.
To illustrate the matching strategy, imagine having two incidents created and searching with the tag cause-04 selected.
  1. Incident with the tag cause-04
  2. Incident with the tags cause-04 and cause-5
Exact match will return incidents that match exactly with the tags you have selected. In the example above only incident 1 will appear in search results, incident 2 will not appear.
Includes will return incidents that contain a singular matching tag. In the example, both incident 1 and incident 2 will appear in the search result.
Excludes will return incidents that do not match any of the tags specified. In the prior example, neither incident will return.

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 using conditions for granular automation.


Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more