Ticket-creating automations are incorrectly enabled by default

Description

In translating the old SQL automations into the new Drools way of doing automations, we overlooked the fact that the createTickets, createCriticalTicket, updateTickets, closeClearedAlarmTickets, and clearAlarmsForClosedTickets automations were disabled by default. This means that on any system migrated from Meridian 2018 or earlier or from Horizon 24 or earlier, on which a ticketer plugin is configured and the ticketer is enabled, a ticket will be created for most every alarm. This is not typically the desired behavior.

We can easily disable these automations by adding enabled false before the rule's when (left-hand) side. This change may result in rpmnew files on Meridian, but the risk of surprise ticket creation likely outweighs the pain of dealing with one rpmnew.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Christian Pape December 19, 2019 at 7:07 AM

Merged.

Jeff Gehlbach December 6, 2019 at 10:52 PM

Fixed

Details

Assignee

Reporter

Components

Sprint

Affects versions

Priority

PagerDuty

Created December 6, 2019 at 10:46 PM
Updated December 19, 2019 at 7:07 AM
Resolved December 19, 2019 at 7:07 AM

Flag notifications