Breaking News!

No comments

You don’t need to use a Microsoft generic Service Level Tracking Summary Report anymore. Savision heard you and decided to collaborate with me on a new project: a user-friendly report that allows you create and export a complete SLA overview of all of your SLOs. Plus it is a FREE community reporting management pack (Click here to download the management pack).

Check out the real benefits of the new report:

  • A complete SLA overview report of all your Service Level Objectives.
  • An easy way to analyze why SLA expectations were not met by drill down and review the top targeted monitoring objects and their alerts causing downtime.
  • This report can be set up once and sent automatically via email at regular intervals.

In other words, no more:

  • Exporting data to Excel to improve the view of format data.
  • Wasting time on complex searches to delve deeper into the data.
  • Explaining to your boss what he sees in the report.
  • Explaining to your boss that SCOM doesn’t have the report he needs.

Note: If you not familiar with SCOM reporting, lately,  Microsoft MVPs Bob Cornelissen and John Barreto joined forces with Savision to create the ultimate 23 pages guide to SCOM reporting (Click here to download this eBook).

How we came up with the project

An SLA is an agreement between clients and IT organizations on regarding the services and quality delivered. SLOs are defined within every SLA to obtain specific and measurable metrics which help to evaluate the quality of the service. Therefore, it is essential to continually track SLAs.

To most users the default Service Level Tracking Summary doesn’t seem to be user-friendly, as you can see in this example:

Table showing SLO performance in SCOM Console
SLA Example token from (

As you can see, if you have more than 10 SLAs the current report can be very confusing and be challenging to manage SLAs situation. Therefore, obviously, a change was needed.

Savision has a vast experienced in optimize IT service delivery, prevent problems, and reduce a service downtime. All those and the willingness to help the community, bring them to collaborate with me on a project to improve SLA report.

The Project Result

At First, without adding additional words here is an example of a report output:


As you can see, the report is straightforward to understand, rows are SLAs and columns are SLOs. The indicators show the availability percentage for a time frame of your choice. To find out why an SLA was not met, you can click on the SLO, and the report will show the top monitoring objects that caused the downtime.


The report also integrates with Live Maps and shows the Infrastructure, Application, and End-User perspectives. If used with regular SCOM SLOs, it will show one column per group within the SLA target, and each column will represent its own SLO percentage.

(Note: It is preferable to select a small number of services at a time to make the report load fast, but keep in mind you can choose a longer list and run a scheduled report in the background.)

Enjoy reading my blog, please don’t forget to subscribe by click on the Following blue button that is on top of the page.

T H A N K  Y O U 🙂

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s