Skip to content

“Pause” SLA in SCSM 2012: Yes, you can

“Pause” SLA in SCSM 2012: Yes, you can published on 19 Comments on “Pause” SLA in SCSM 2012: Yes, you can

imageThis is not a technical article but some kind of news. With SLA feature you can create a “rule” how to apply SLA to SCSM’s objects like incidents or service request (or any other object). If you don’t know how to do that please welcome to Rodney’s blogposts series: Part 1, Part 2 and Part 3.

But many peoples ask the one question: can we pause SLA depend from status or anything else? For example, how to stop SLA timer if status of incident changed to Pending? Before this week all who answer on this question (me too) ask “No, it’s possible”. But in fact you can (but see the note and the end of this article).

To demonstrate this I’ve created new SLO with next parameters:

Queries: High Priority incidents (all incidents with Impact and Urgency = High)
Calendar: 24×7 (every day from 00:00 to 23:59)
Metric: Incident – Resolution time
Warning Threshold: 2 hours
Target: 10 hours

Newly created incidents already has a SLA object:

As you can see target date is 07.08.2012 02:42 (CreatedOn + 10 hours).

After modification of the workflows settings (see next blogpost, XML coding of course) we can use Pausing feature. Let’s change status of our incident to pending:

Now let’s see what’s happened with SLA object:

As you can see the SLA object now is in Paused state and there is no more “Time before SLO breached”! Some time later I’ve changed incident’s status back to Active:
Note to time: time span between two state changes is a 1 hour and 3 minutes (17:21 – 16:18). Now let’s see to SLA object:

Look at  the “Target End Date” field. Now it’s equal to (CreatedOn + 10 hours) + 1 hour 3 minutes. What mean it’s longer on period when incident was in Pending state.

NOTE: Something telling me what this feature added as unsupported. Try to investigate that and let you know.


%d bloggers like this: