Other Incident Settings

Incident Tag Prefixes

Located at Settings > Incident settings.

When configuring Incident Tags, organizations can require specific tag prefixes from responders. This enforces that all tags must start with any of the specified prefixes, which can ensure data cleanliness and consistency. For example:

All tags must start with "dev-" or "prod-"

All tags must start with "dev-" or "prod-"

Attempting to set a tag that doesn't fit the above criteria:

You get an error

You get an error

Suspect changes window

Example of suspect changes window set to 1 day

Example of suspect changes window set to 1 day

Located at Settings > Incident settings.

FireHydrant's Change Events offer a powerful way to ingest any changes that occur into your system and associate them with different components of your Service Catalog. When conducting incidents, FireHydrant will automatically associate recent change events within a certain window of time before the event so responders can look at which changes may have potentially triggered the incident, if any.

The default time window is 1h, or 1 hour before the start of the incident. Users can modify this value as needed.

Incident nudge duration

Example of nudging set for 1 hour of inactivity

Example of nudging set for 1 hour of inactivity

Located at Settings > Incident settings.

You can configure FireHydrant to "nudge" or remind users that there's an open incident to which they are assigned role(s). The amount of time of inactivity before nudging can be configured, and as part of nudging, we will also show the nudged user options for handing off their role, which will automatically re-assign all open tasks to the person being handed off to.