Monitoring your IT Services with SCOM can be quite tricky to realize, but becomes more and more important. Do you want to know how to get your Services monitored, fast and efficient?
SCOM Service Monitoring
Most people that are looking for SCOM service monitoring are probably looking for information about how to monitor a Windows Service with System Center Operations Manager (SCOM). However, it is also possible to monitor IT services with SCOM. In SCOM, they name an IT Service a ‘Distributed Application’, mainly because most System Center users think of a Windows Service or Web Service when they see the word ‘service’, instead of an IT service.
An IT service is very well-known by people who are familiar with IT Service Management (ITSM) solutions, whereas a Windows Service is well-known by people from IT Operations. Live Maps Unity is the solution to bring those two worlds together. IT processes – like incident management and change management – will be easier to manage when you know exactly which IT Component, like a Windows Service, is ‘partly’ responsible for the functioning of a specific IT Service. For example, if you can automatically relate an incident on an IT component to the IT service, the information about which IT services are impacted by the incident is one mouse-click away.
Monitoring a Windows Service
In case you are looking for how SCOM can monitor a Windows Service, I will try to give a short summary of how SCOM monitoring works. In most cases, SCOM monitors much more than only the Windows Service. For example, SQL Server is also implemented using Windows Services, and SCOM doesn’t only monitor if those Windows Services are running or if there are certain events in the event log. SCOM uses more than 40 monitors to monitor the health of the SQL Server Windows Services.
Read our complete blog post here. The blog post is written by Savision’s Lead Developer, Klaas Hulder.