Self-Monitoring

The end-to-end monitoring and alerting infrastructure (MAI) allows stable and reliable operation of complex heterogeneous system landscapes. To monitor the correct functioning of the landscape, a large number of metrics and alert types, as well as various views and applications, are available to you, which provide prior warning about possible problems. So Self-Monitoring keeps you informed about the trustworthiness and timeliness of the monitoring data, and - if there are any issues - how to resolve the issue.

Self-Monitoring has different aspects:

  • Monitoring of the MAI and other central functions

  • This feature contains functions that display specific metrics, alerts, and logs and traces for the central infrastructure of SAP Focused Run. In the overview view of Self-Monitoring, this information is grouped by the following central components:

Central Component

Description

Agent Management Application

The Agent Management application manages simple diagnostic agents installed in all managed systems, centrally. In Self-Monitoring, the status of the data collection regarding agent errors, configuration issues and availability checks are displayed.

CSA Collector Framework

The CSA Collector Framework stores the configuration data of the managed systems, allowing you to trace configuration changes. It is also used for scheduling, sending and processing these data; in Self-Monitoring, the status of the Collector Framework is displayed.

Introscope Enterprise Manager

CA Wily Introscope Enterprise Manager (EM) acts as the central repository for all Introscope performance data and metrics collected in an application environment. In Self-Monitoring, metrics for availability, health and capacity of the EM are displayed.

SAP Early Watch Alert Reports Infrastructure

SAP EarlyWatch Alert Reports is a diagnostic service, which monitors solutions in SAP systems. SAP Focused Run transfers the service data collected from the managed system to SAP Support Portal, where data is analyzed and a report is created.

Monitoring and Alerting Infrastructure

The Self-Monitoring displays specific metrics and alerts to monitor the correct functioning of central components belonging toMAI. Including Event Calculation Engine and Unified Metric Store.

  • Self-Monitoring of Managed Systems

    To be able to monitor managed systems, the monitoring for these systems needs to be correctly set up, the associated agents and monitoring functions need to be working correctly, and it must be possible to connect from the SAP Focused Run system to the relevant managed system without problems. In the system view, this information is displayed, grouped by technical systems.

  • Self-Monitoring features within System monitoring

    The status and values of the Self-Monitoring metrics are integrated into System Monitoring, both on system and on metric level.

Features

Generally, in Self-Monitoring the following functions are available to you:

  • For each metric and alert type, you can display a description that provides information about the meaning of the metrics and, if there is an error status, about the meaning, consequences, analysis, and possible solutions of the error.

  • You can display the development of performance metrics over time, in the Metric Monitor.

  • Appropriate analysis and troubleshooting tools are available to you at the level of metrics, but also at the level of central components. You can call these tools directly from the Self-Monitoring user interface. When you call these tools, additional context information is passed, so that corresponding filters are set to display only the information that is related to the affected object in the appropriate tool.

Monitoring of the MAI and other central components

If you want to monitor the components of the MAI or other central functions of SAP Focused Run, use the Overview of the Self-Monitoring in the tab Central Components. Here, the most important metrics are displayed, together with their status and the number of associated alerts, broken down by the central components listed above.

Self-Monitoring of Managed Systems
If you want to display the Self-Monitoring of the managed systems, use the Managed System View. You can filter the systems displayed according to different criteria:
  • Data Separation (systems belonging to a customer or a data center)

  • Properties or roles of the technical system

The Managed System View checks, among others, if the following prerequisites are fulfilled by the managed systems:
  • The properties of the system in the Landscape Management Database (LMDB) are automatically updated by SLD data suppliers.

  • The agent and the Introscope Enterprise Manager responsible for the system are available, running without errors and the configuration settings of the agent match those stored centrally in SAP Focused Run.

  • The configuration data of the system is sent via the CSA Collector Framework

  • The configuration of the system using Simple System Integration was successful.

  • The transfer of the ABAP statistics data aggregates to the managing system was sucessful.

Self-Monitoring features within System monitoring

In System Monitoring, alerts and metrics of Self-Monitoring are displayed on system level utilizing the fact that Self-Monitoring is a monitoring category like availability, performance, configuration and exceptions. That means that next to the monitoring values of your managed systems the trustworthiness and timeliness of these values are displayed.

On metric level, you can check the data collection, which leads to Self-Monitoring information and troubleshooting tools for this metric.

Self-Monitoring Dashboard

The Self-Monitoring Dashboard is a central place to see the health of the system. It displays the Monitoring and Alerting Infrastructure (MAI) engine runtime during a specified time period, to evaluate the performance of the different MAI tasks. This job SAP_ALERT_CALCULATION_ENGINE uses the reported metric values to determine the status, events, and alerts of the administered objects on the basis of configuration settings. Besides the calculation of events it allows event correlation and propagation. It runs by default every minute, so the runtime should always be well below a minute.