SLA-based management is a much simpler way to manage an environment because it lets you group servers together by their importance to the company. Every server you have isn’t as important as every other server, so knowing which servers are the most important helps IT personnel as well as managers know what the company considers important. As well, it’s much easier for you to know that Server1 is a Gold server because you know what that means. You know how Gold servers are treated in your environment, and all Gold servers get certain level of treatment. So when you bring on new servers, you classify it as Gold also, and it automatically gets the treatment that all the other Gold servers get. And if you want to change an SLA for a server, you have but to make the change in a single table in ME and that server is automatically treated as the new SLA. It’s a single change in a single place.
In ME, we separate 3 different SLAs: Gold, Silver, and Bronze. We could have gone with T1, T2, and T3, but we liked the precious metals. Every server you have must be classified into an SLA. Every collection we run pulls info from each server based on its SLA in the system.
Assigning SLAs
So how do you assign an SLA to a server? It’s very easy. Just go to the dbo.Servers table and change the ServiceLevel column. There’s nothing else to it. And if you need to chance an SLA you do it the same way.
Creating your own SLAs
You can, of course, create your own SLAs inside ME too. It’s not as easy as being a one-click operation, but it’s still quite doable. You can either add a 4th level like Platinum, or Jade, if you like, or you can get off of the precious metals completely and complete rename all the SLAs in the system. We call this “recoloring the system”. When you recolor the system, you have to make changes to the following areas:
- Change the ServiceLevel column in dbo.Servers.
- Change the names of the query files for the collectors.
- Change the SLA info in the jobs.