Portal - SLO Time Difference VS Console
Hi Guys,
I'm noticing some strange inconsistency on the Portal Vs SCSM Console, and I can't quite figure out what's going on.
If I look at a job history and check the time that it was raised on the portal. this matches what I have in the SCSM console, but if I view the SLO applied to a job in the console and then match it to what the portal is showing me, I see a very BIG difference!
As you can see, the SLO should be at 134 hours, but the portal clock icon shows 502 hours! I could understand if this was an hour ahead or behind as it might just have something to do with daylight saving time, but I can't understand why the difference here is so huge. Has anyone else experienced a significant difference in time?
The time zone setting on my Service Level Calendar is at UTC Dublin, Edinburgh, Lisbon, London - and we only have this time zone on our estate. Although saying that, its a setting within Service Manager so it would be the same in the console if this was the cause, so I'm fairly certain its Cireson.
Is there a menu or a localisation option or time zone setting that I might have missed that someone may have seen before?
P.S
I have a test system which I have wiped the CustomSpace directory on and I'm still seeing the same sort of difference in time remaining on calls in the portal vs the console.
Thanks
Best Answer
-
Joe_Burrows Cireson Devops Super IT Monkey ✭✭✭✭✭Hi Zac
Checkout the below thread I posted on this FAQ:
https://community.cireson.com/discussion/12/support-faq-why-does-the-slo-countdown-in-the-portal-different-to-the-scsm-console
Any questions let me know.
Cheers
Joe5
Answers
Checkout the below thread I posted on this FAQ:
https://community.cireson.com/discussion/12/support-faq-why-does-the-slo-countdown-in-the-portal-different-to-the-scsm-console
Any questions let me know.
Cheers
Joe
Ah! Thank you! I did try to search but for some reason I didn't come across that one. That explains it, at least I know its not something that I've screwed up. I'll let my colleagues know as when I originally saw it, I presumed it was a bug.
Thanks