For a long time I got stuck in the mindset that a Service Level Tracking item (SLT) contained a single Service Level Objective (SLO). A single SLT can be created which contains multiple Service Level Objectives (SLO’s). As an example, service levels may include or not include planned maintenance windows. The example discussed in the blog entry shows a single SLT which has two different SLO’s. One SLO which does not include planned maintenance and has a 99% uptime requirement. Another SLO which does include planned maintenance and has a 95% uptime requirement.
TIP: When naming your service level objectives, put the unique portion of the SLO in the front of the name. Only the first 22 characters are displayed on the dashboard. It is more intuitive to see “Planned Maintenance – “ than to see “Operations Manager – P” on the dashboard. See the graphic below for an example of how not to name the SLO’s.
When we are creating the SLT we can define multiple SLO’s as shown in the graphics below:
Using the SLD dashboard, we can display both of these different SLO’s together as shown below.
Summary: Don’t get stuck in the mindset that an SLT can only contain a single SLO. In OpsMgr different SLO’s can be defined based upon what states are considered as downtime. These different SLO’s are still displayed together in the SLD dashboard and SLD reports.