Non-SAP Monitoring Implementation Process
Before starting with the monitoring implementation for a non-SAP system there are several prerequisites which has to be fulfilled. Otherwise you do not need to proceed with the following section because sooner or later you will run into problems.
- In the "SAP Solution Manager: Configuration" workcenter the "System Preparation" needs to be successfully executed. For details you can check the "SAP Solution Manager Setup" wiki -> "System Preparation with 7.1"
- In the "SAP Solution Manager: Configuration" workcenter the "Basic Configuration" needs to be successfully executed. For details you can check the "SAP Solution Manager Setup" wiki -> "Basic Configuration with 7.1"
- The "Managed System Configuration" for the Solution Manager System itself needs to be successfully executed.
- The "Technical Monitoring" setup for the Solution Manager System itself needs to be successfully executed.
- You should already have some system monitoring experience
- You should have a technical understanding of the new Monitoring and Alerting Infrastructure (MAI)
The following diagram provides an overview of the different activities to be done. By following this process you can easily setup monitoring for a non-SAP system. The chapters below provide details on the individual step and in most cases there is a how-to guide available showing a real example.
In addition to the general prerequisites on top there are some system specific preparations which need to be done.
Installation of Diagnostics Agent and SAP Hostagent
Most of the metrics in the non-SAP environment are collected via the Diagnostics Agent and the SAP Hostagent. Please refer to SAP note 1833501 and 1858920 for the installation of the Diagnostics Agent.
In case of a high available non-SAP system it might be necessary to setup the Diagnostics Agent as an "on-the-fly" agent. Please refer to "Diagnostics Agent and HA Support" wiki page for details.
Installation of Introscope Bytecode Agent (OPTIONAL)
Most of the monitoring metrics for non-SAP systems can be collected via Diagnostics Agent and SAP Hostagent. For the performance monitoring of Java and .NET based systems we rely on CA Introscope metrics. SAP Solution Manager includes a so called "Right to View" license which can be used for all applications sold by SAP. To use CA Introscope for non-SAP system requires a "SAP Extended Diagnostics by CA" (SED) license which can be bought from SAP. Below a comparison of the "Right to View" versus the "SAP Extended Diagnostics by CA" license:
Once you have the SED you will get the full version of CA Introscope with unlocked agents and additional instrumentation for common third party middleware products. It also includes Introscope agent installation guides.
In case you already have a SED license please refer to SAP note 1280961.
Technical System Creation
One feature of the new Monitoring and Alerting Infrastructure (MAI) of Solution Manager 7.1 is its landscape awareness. This means Solution Manager knows the system landscape and maps the monitored metrics to the landscape objects, which are the so called Managed Objects (MO). The following picture provides an overview of the available MO in system monitoring:
For mainstream SAP systems normally report their landscape information is reported automatically (via a SLD data supplier -> SLD -> LMDB) to the Solution Manager. For non-SAP systems there is normally no automatic SLD data supplier and the landscape information needs to be maintained manually in Solution Manager. This is a quite simple process and is described in the how-to guide "Creating Unspecific Cluster System".
Managed System Setup
After the non-SAP system was created in Solution Manager the managed system setup needs to be done for it. The main purpose of the managed system setup for non-SAP systems is the following:
- getting the diagnostics agent assigned to the non-SAP system
- assign the Introscope Enterprise Manager to be used for the non-SAP system
- setup of the system related extractors and the Introscope Hostadapter (part of the Diagnostics agent)
Like for SAP systems you just have to follow the managed system setup guided procedure. It is also described the how-to guide "Creating Unspecific Cluster System".
Up to now we just prepared everything for the real monitoring configuration which is done in this section.
First you need to know what you want to monitor in your non-SAP system. There are basically three categories which make sense for non-SAP systems:
Once you know what you want to monitor you need to configure the metrics and alerts in the monitoring templates. On system and instance level there are so called "generic product version" templates which are empty templates and we use them for the non-SAP purpose. On host and database level the existing SAP templates can be used.
Finally the templates will be assigned in the "Setup Monitoring" step to the non-SAP system and monitoring will be configured with them. Further details and examples you will see in the below mentioned how-to guides.
System and Instance Level Metrics
System and instance level metrics are the non-SAP system specific metrics. A good starting point is always the availability of the system and some exception related metrics. Finally also performance metrics can be configured but as soon as CA Introscope is required a "SAP Extended Diagnostics by CA" license is required. In the following sub-chapters some examples for the different categories are provided.
- URL Monitoring: You can check the availability of an URL based on the http status code. For more sophisticated cases you can also check the content of the HTTP response using a regular expression. An example for this is described in the how-to guide "Availability Monitoring using Http Ping".
- OS Process Monitoring: You can check the existence of OS processes based on a process name pattern. An example for this is described in the how-to guide "Monitoring OS processes with MAI".
- OS Script Monitoring: The OS script monitoring data provider gives you full flexibility. The diagnostics agent regularly executes a custom OS script and the result of the script can be evaluated. So this is not restricted to availability only. You can also use this for exception and performance metrics. It only depends on custom script. An example for this is described in the how-to guide "non-SAP Monitoring using OS Scripts".
- Log File Monitoring: You can do a text pattern search in log files, check for specific file attributes or monitor the Windows event log. Details and examples you find in the Solution Manager documentation on help.sap.com in the chapter "Monitoring Log Files in the Monitoring and Alerting Infrastructure".
- OS Script Monitoring: The OS script monitoring data provider gives you full flexibility. The diagnostics agent regularly executes a custom OS script and the result of the script can be evaluated. By this you can also report exceptions. An example for this is described in the how-to guide "non-SAP Monitoring using OS Scripts".
- Introscope Monitoring: As mentioned above you need to have a "SAP Extended Diagnostics by CA" license in case you want to use Introscope for your non-SAP system. Once Introscope is in place and you see the metrics you want to monitor in the Introscope Enterprise Manager they can be included into the monitoring. An example for this is described in the how-to guide "Custom Introscope Metrics".
- OS Script Monitoring: The OS script monitoring data provider gives you full flexibility. The diagnostics agent regularly executes a custom OS script and the result of the script can be evaluated. By this you can also report performance metrics. An example for this is described in the how-to guide "non-SAP Monitoring using OS Scripts".
Host Level Metrics
The host level metrics you get out of the box by using the standard SAP host templates.
Database Level Metrics
For the database level metrics you can also use the standard SAP database templates. But there is one additional prerequisite. The Monitoring and Alerting Infrastructure gets most of the database metrics from the DBA Cockpit of the Solution Manager. This means that the non-SAP database needs to be connected to the DBA Cockpit. In order to connect the database, depending on the database, some scripts need to be executed on the non-SAP database which create some monitoring related tables and configures the data collection into these tables. For further details check the relevant SAP notes for the DBA Cockpit connection.
Depending on the metric configuration, all metrics measured in the Monitoring and Alerting Infrastructure of Solution Manager 7.1 can be written into BW of Solution Manager. Hence a reporting can be built on top of this data. How to build custom reporting is not part of this wiki.