Highlighted
Respected Contributor.
Respected Contributor.
198 views

SLO starting early

Hi Experts,

   I've noticed one of our SLO-s firing too early. The corresponding caldutyhours table sets the working hours from 10:00 to 17:00. The IM ticket has been opened at 20:31:01 and the SLO started immediately. How come? No calholiday or any other exeption... the SLO type is the very same on the sloresponse ticket: everything adds up, but still, the IM slo started up way to early.

Any ideas?

BR, Dávid

0 Likes
1 Reply
Highlighted
Honored Contributor.
Honored Contributor.

Re: SLO starting early

What you mean by started immediately? start.time is equal to the time ticket landed in the "Initial State" and is the expiration.time falls outside of your caldutyhours in sloresponse table? Is the caldutyhours defined in the SLO "schedule" field?

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.