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:
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.