Availability Monitoring
Last updated
Last updated
Availability Monitoring determines the operational status of an application, service, or infrastructure component. It is a vital aspect when monitoring systems and applications. However, availability information alone is not useful without the service context and its relationship to Service Level Objectives (SLO).
SLO defines the desired availability (i.e., percentage over time) and how it should be measured (i.e., sampling interval and calculation window).
The availability of services can be very different from component availability.
In the context of monitoring SAP, you must understand that the application is just a portion of an entire system landscape.
For example, consider SAP ERP, an SAP application, which may appear to have uninterrupted availability for end-users. However, one or more of its underlying infrastructure components, such as application servers, message servers, enqueue servers, and database servers, can experience intermittent downtime.
If the architecture is deployed with the appropriate high-availability (HA) configuration, where infrastructure components will have redundancies to ensure all the single points of failure are covered, then the service may be 100% available while the redundant components can be less than 100%. With proper service monitoring, these can be properly distinguished and managed accordingly.
IT-Conductor can monitor the availability of user-defined services and the supporting infrastructure components with more flexibility. Using the platform's parallel processing engine, service availability monitoring would be simplified by depicting a correlation of the individual components of the operating system in such a way that you can easily see at a glance if a service is available or not, in relation to the other dependent components as well.
