Enhanced Tag Management Settings
Tagging incidents is the primary way for incident responders to add context to incidents, to help with the investigation during and after the resolution of an incident, during retrospectives, and for post-incidents data analysis using Blameless Reliability Insights.
Blameless has enhanced how predefined tags and tag categories are managed in the Blameless suite, while the process of adding predefined or free-form tags to incidents remains the same through Slack, Microsoft Teams and the Blameless web UI.
The new centralized Tag Management Settings allows creating and administration of predefined tags into tag categories with the following new enhancements.
Newly created tag categories apply to all incident types by default unless restricted to specific incident types
Easily add an entire list of predefined tags to a tag category by copying and pasting a string of tags separated by commas
New option for tag categories to require incident responders to select a single predefined tag instead of multiple
New option for tag categories to require predefined tags to be added to incidents before resolving incidents
Consolidate tags from multiple tag categories into one tag category using the new merge option
Archive tag categories that should no longer be used for new incidents, while preserving references to archived tag categories under existing incidents and for post-incident data analysis using Blameless Reliability Insights.
- Archived tag categories can be restored at any time.
- Duplicate a tag category, including its predefined tags, to simplify and accelerate the creation of new tag categories
Blameless is not creating a net new incident assuming that Pagerduty has already submitted a similar alert. (INTG-338)
When a new Pagerduty alert auto-triggers the creation of a new Blameless incident using a Blameless inbound webhook, Blameless detects that the Pagerduty deduplication key for this alert is the same as a previously received Pagerduty alert.
This prevents it from starting a new incident, although the expected intent was to start a new incident.
Blameless now creates a unique Pagerduty alert each time and ignores the deduplication key of the received Pagerduty alert, therefore relying now on the Pagerduty incident creation policy when a Pagerduty alert triggers in Pagerduty.
This may or may not require creating a new incident for similar alerts (e.g. same subject).
Please refer to your Pagerduty documentation on how to configure your incident creation policy to meet your specific use case.