SLA Management in Live Maps Unity 7.5 by Daniel Örneling

One of the most important aspects when working with business services and monitoring is to know whether they are performing as expected or not. With Operations Manager, out-of-the-box, this isn’t quite as easy as you would want it to be. For some years now, Savision has delivered the best solution that I know of to help monitor these business services and to also make sure that you can measure the availability of the services. With their latest release of Live Maps Unity 7.5, this is taken to yet another level.

In earlier versions, you have gotten alerts when parts of, or the complete service is considered to be down and not functioning. This has, of course, been a great help but it hasn’t generated any alerts on whether the SLA levels are met or if they’ve been breached. With this new version of Live Maps Unity, the possibility to monitor the SLA levels has been introduced, as well as the status of the service.

So how is this done and what does it look like?

Once you have created a business service, all of the components are being monitored “together” instead of separately as single objects. What I’m going to show here is how to set up these SLA levels and also how to configure SLA alerting. The first thing you see when you open up an existing service – as I´ve done below – is some general information about the service and a description etc. Click on the Service Level tab.

Service_Properties

Service Properties. Click on image to enlarge.

Once you see this view, you have the opportunity to configure different SLA levels for different layers of the service. You can also choose to only use business hours to measure the SLA levels. This is a great feature which will be used depending on what kind of service it is that you´re monitoring. If you’re monitoring a website that is only supported between 8 am and 5 pm (08:00 – 17:00), the end-user perspective could be configured with a SLA level of, let’s say, 99.9 percent during business hours. This means that if the end-user parts of the service go down outside of these hours, you won’t get a dip in your SLA curve.

Service_Level_objectives

Application Component Availability.

To configure the SLA levels of the end-user components, set a goal as I’ve done below at 99 percent and then set the business hours.

Service_Level_objectives_2

End User Component Availability.

Those were the end-user components. To find out about an SLA for the complete service, click here and read the full blog.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.