Skip to main content

Occasionally we’ll see false alarms in PagerDuty due to an upstream issue coming from Splunk or New Relic. These are alerts that fired due to testing, maintenance, or some other event that we don’t want to “count” as real production incidents. I don’t see an ability in the tool to archive/hide/etc. these events so that they don’t clutter up our reporting & analytics. 

 

Anyone else have a solution or approach to manage these? 

@Jon Hanseling Currently, there is no way to delete or archive incidents or alerts. I brought this up to the Analytics product team as a possible use case for types or fields as a way to flag incidents, such as a “false alarm” incident type. The team shared that this is being planned for later in Q4.

Reply


Terms & ConditionsCookie settings