SLO objects duplicating responses and triggers in V12

Document ID : KB000122924
Last Modified Date : 14/02/2019
Show Technical Document Details
Issue:
The SLO engine is firing the response action for a violation of a service 2 times, resulting in 2 notifications when only one should be received. It is also further triggering an SLO violation in some cases 3-5 times for the same violation on the same workflow/RunID.
Environment:
Any Version 12+ Automation Engine.
Cause:
This behavior has been identified as erroneous, and will be addressed in a future release. Behavior:
 

During the check for latest start and latest end in one timer, SLO objects with the same name are checked. For example:

SLO_MC.0200.PST

This works well if the SLO object exists in multiple clients with the same name.

The problem arses with the SQL statement that checks if there are already violations or start entries because it uses the name of the SLO (and ignores the client):

SELECT COUNT(*) FROM LASLM WHERE LASLM_SloName = ? AND LASLM_DetectTime > ?

This can cause multiple violations for the same service RunID.

Resolution:
This issue has been found and identified for release in the following components/versions:

Fix Version/s:
Automation.Engine 12.0.7 - released, available on the download center.
Automation.Engine 12.1.4, Released, available on the download center.
Automation.Engine 12.3.0, planned release April 23rd, 2019.
Automation.Engine 12.2.2 , planned release February 28th, 2019.
Additional Information:
There is no known workaround for this issue. If upgrading to one of the above releases does not resolve the issue, please open a ticket with Support and reference this knowledge article.