Cireson Portal + Response Time SLO
Did I miss something?
Best Answer
-
Brett_Moffett Cireson PACE Super IT Monkey ✭✭✭✭✭That's the answer.... The Workflow itself was stuck rather than the portal being the source of the issue.
Workflows can get stuck from time to time if the system resources are low or there is something holding up the works.
Without sounding too much like a sales guy, Cireson can assist you with a health check of your environment if that would help.
Or if budget is an issue, then take a deeper look in to the core SCSM environment and keep an eye on the system resources over time. Especially overnight when a lot of the daily workflows and reports are run.
Good luck.6
Answers
If the First Response date is being set and the SLO is not acknowledging that the date has been set then I would check the SLO first.
Have a look at the Metric that has been created and check that the start date is set to the "Created Date" and the end date is "First Response date".
Also make sure the Queue that has been selected contains the IR that you are testing it on
and finally that the SLO is enabled (Which it sounds like it is)
My feeling is wither the Metric or the Queue is the issue.
Good luck. I hope this has answered your question.
Metric is targeting class Incident with start date of "Created Date" and end date of "First response date".
Metric shows as being related to my P4 Response SLO in the "Related SLO(s)" section.
Work item shows the relationship changes as below. SCSM console shows the SLO as still active.
Also in the history of the IR shows the relationship to the specific queue "V1 IT SLO - P4" being added.
I'll mention that the IR is now part of two queues. One for the team who'll process them WI, one for the SLO. Hope that's ok?
From what I can see the portal is setting the First Response date fine so the Metric should calculate the time between the created date and the first response date and act accordingly.
Can you post some screen shots here of your SLO and Metric just to rule out everything?
Screenshots below.
I'm also going to refresh the Health Service store on the primary workflow. Seeing manual activities not enter an In Progress state. Wondering if it's linked.
Workflows can get stuck from time to time if the system resources are low or there is something holding up the works.
Without sounding too much like a sales guy, Cireson can assist you with a health check of your environment if that would help.
Or if budget is an issue, then take a deeper look in to the core SCSM environment and keep an eye on the system resources over time. Especially overnight when a lot of the daily workflows and reports are run.
Good luck.
CPU utilisation on our primary workflow server is spiking to around 60% at night. Memory load also around the 60% mark. I don't include the workflow server in our web front end group to try and avoid resource issues.
In my experience IO is the key piece that prevents the system from doing what it needs to do in enough time.
We have similar problem. @Tom_Hendricks explained in detail in my thread here: https://community.cireson.com/discussion/5046/sla-first-response-not-caught#latest