Advanced Monitoring is a functionality on top of System Monitoring, which addresses certain inflexibilities in the template approach. Some areas of monitoring are typically very specific, and the monitoring settings are different for each managed object. Using Advanced Monitoring, you can easily configure certain monitoring objects directly for selected managed objects, without having to configure them in the System Monitoring template used. Advanced Monitoring should not be regarded as a completely new use case, but rather a complementary functionality in the context of System Monitoring.
Configuration of Advanced Monitoring is performed using dedicated Guided Procedures for the currently available areas of monitoring:
- Oracle Tablespace Monitoring
- ABAP Transaction Monitoring
- File System Monitoring
- URL Availability Monitoring
Within the configuration, you can easily add/remove/change metrics, maintain thresholds (individually or for several metrics at once), define settings for automatic creation of incidents and notifications etc. Advanced Monitoring is fully integrated with the Monitoring and Alerting Infrastructure (MAI). The monitoring status is integrated into the System Monitorng UI. Alerts are shown in the Alert Inbox.
- Transaction GPA_ADMIN (or via SAP Fiori Launchpad, tile Guided Procedure Catalog in the tile group Guided Procedures):
- Type: Guided Procedure
- Application Area: Advanced Monitoring Configuration
- Select the appropriate Guided Procedure and execute it
ABAP Transaction Monitoring
The principle is the same in all four cases. ABAP Transaction Monitoring shall be used to demonstrate the configuration procedure.
In the first step of the Guided Procedure, select the ABAP system for which monitoring is to be configured and click Next to go to step 2. You will be asked to activate monitoring if not done so already. You can also click Activate Monitoring. This is a prerequisite to configure metrics in step 2.
Via the button Create, you can create new metrics. Provide all necessary details and click OK:
The metric will be added under the alert Bad Transaction Response Time. In the UI, you can change metric definitions including thresholds. Note that you have to be in the Metric View to be able to maintain all metric settings:
Besides the Transaction Response Time, you can also monitor the Number of steps (to be selected in the column Key Figure). Furthermore, you can also the time granularity for evaluation of the key figures.
The Transaction Response Time is measured in milliseconds.
By selecting the alert (first line), you can maintain alert settings. All changeable alert settings are available in the Alert View:
You can change the severity of the alert and maintain settings for automatic incident creation via SAP Solution Manager ITSM, automatic notifications (email or SMS) and forwarding of the alert via the Alert Consumer BAdI interface. Currently, it is only possible to maintain this via variants (click on Maintain Variants... on the respective tab to create or change variants).
You can manually check the data collection using the Test button.
When the configuration is complete, click Save. The monitoring will be active afterwards.
Oracle Tablespace Monitoring
The configuration of Oracle Tablespace Monitoring is similar to ABAP Transaction Monitoring. Important aspects are:
- In step 1, only Oracle databases can be selected.
- In step 2, a button Add Tablespace is offered, which allows to pull the information about available tablespaces directly from the connected database. You can decide for which tablespaces monitoring shall be configured.
- Alternatively, you can configure metrics via the Create button (name of tablespace has to be inserted manually).
- The available key figures are Free Space (MB) and Used Space (%).
File System Monitoring
The configuration of File System Monitoring is straightforward. In step 1 you select the host for which File System Monitoring is to be configured. In step 2 you can create metrics via the Create button. Via Upload Filesystems you can also import a list of file systems as a CVS file. Create one line per filesystem and use the syntax filesystem,metric_name (where metric_name is optional).
The key figure is File System Used, measured as a percentage.
The name of the filesystem(s) to be monitored can be defined using regular expressions.
In URL Monitoring you can define a list of URLs which should be additionally monitored in the context of a technical system. Typical use cases are URLs for a Web Dispatcher or 3rd party load balancers which need to be available to access a system. For the maintained URLs you can check the availability and the https certificate of the URL.
Note: The setup is performed in the context of a technical system. I.e. a Diagnostics Agent assigned to that technical system is used to perform the measurement. The URL to be checked can be any URL which can be reached from the host where this Diagnostics Agent is installed. The result will be displayed in the availability category of the system.
The procedure to configure the URLs you want to monitor on a technical system is similar as explained for the other scenarios above:
- In step 1 of the respective Guided Procedure, select the system where the URL checks should be performed.
- Click Activate Monitoring, if not done yet.
- Click the Next button (or select the step 2 Monitoring Configuration on top).
- Click on Create.
- Choose the key figure type. Possible options are:
- URL Availability: Checks if the URL is available.
- URL Certificate Check: Checks if the certificate is currently valid.
- URL Certificate Lifetime: Returns the number of remaining days until the certificate expires. It will provide a red rating if the certificate is valid for less than 30 days.
- Enter the URL to be monitored.
- Click OK
- You can repeat this step to monitor multiple URLs or different key figures for a URL
Click "Save" after you have added all your metrics. This will activate the metrics and start data collection.
The events and metrics from Advanced Monitoring are integrated into the technical system hierarchy in the System Monitoring UI. They are visible in the respective category of the managed object to which they refer:
- ABAP Transaction Monitoring: category performance for technical system
- Oracle Tablespace Monitoring: category exceptions for database
- File System Monitoring: category exceptions for host
- URL Monitoring: Availability for technical system
In case thresholds are exceeded, alerts will be created and shown within the Alert Inbox. The above said about categories and managed objects also refers to alerts.
As an example, the integration of ABAP Transaction Monitoring into System Monitoring is shown below: