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 command in an active incident channel in Slack and typing the tag name.


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 command in an active incident channel in Slack

Querying by tags

Currently, you can query incidents using tags in the incidents page, the analytics page, or through FireHydrant's API.

Within the incidents page, after you have selected one or more tags, you can select a tag matching strategy. For example, imagine having the following two incidents created: 
  1. Incident 1, tagged with cause-04
  2. Incident 2, tagged with cause-04 and cause-05
Let's assume that you run a search using the tag cause-04.
  • An Exact match search returns incidents that match only the tags you have selected. In the example above, only Incident 1 will appear in search results.
  • An Includes search will return incidents that contain a singular matching tag. In this example, both Incident 1 and Incident 2 appear in the search result.
  • An Excludes search returns incidents that do not match any of the tags specified. In the prior example, neither incident will be returned.

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..


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

Articles in this section

See more
Contact Our Support Team
Got a Question or Suggestion? We're here to help!
Follow us on Twitter
Get the latest news and updates first