-
Request for existing cases, user IDs, Portal navigation support and more
System Analysis
System Analysis in SAP Focused Run is intended as tool for detailed monitoring and analysis of a small group of systems. For this purpose, System Analysis comes with a set of predefined dashboards for common system types and offers the option to compose custom dashboards based on a large catalog of metrics available from different data sources.
- Flexible filtering and display options offer a variety of choices for graphical or tabular display.
- For detailed monitoring, System Analysis offers to optionally collect fine-grained performance data like samples from ABAP work processes and HANA thread samples.
Starting with SAP Focused Run 2.0 FP01 there is also an Open KPI Store, which makes it possible to include any time series of numeric values with some identifiers in one generic table and display the result in a chart of System Analysis.
Available Data Sources
The following data sources can be consumed for displaying data:
Data Scource | Description |
---|---|
System Monitoring (Monitoring & Alerting Infrastructure) | All metrics available in System Monitoring (collected via the “Monitoring and Alerting Infrastructure”) can be consumed in System Analysis dashboards. Beyond this even metrics not visible in System Monitoring, but marked with the "RCA" flag in the monitoring templates, can be used. Custom monitoring templates can be used in the same way. |
Aggregated System Monitoring Data | System Analysis provides a dedicated data store to retain a long-term history of selected metrics. The System Analysis dashboards seamlessly combine data from the System Monitoring store (which typically has a limited retention time to save space) and the aggregated store. |
RCA / Hypercare | There is a group of data stores for root cause analysis. Details are listed in a separate table below. |
ABAP aggregated statistical records (“ST03 data”) | Collection of ST03 data (hourly and daily aggregates) is automatically scheduled as part of simple System Integration. Note: This functionality is shared with “Real User Monitoring” |
ABAP Exception Details | Details on various types of ABAP exceptions (short dumps, Gateway errors, Syslog errors) can be collected regularly and displayed in System Analysis. Note: This functionality is shared with “Advanced Integration Management” |
HANA Ad-Hoc SQL | For HANA databases details can be retrieved ad-hoc via a pre-defined list of analysis statements. |
Available RCA Stores
The following table shows which capabilities are available for intensive monitoring detailed Root Cause Analysis (hyper care). Most of them are not enabled by default (when executing Simple System Integration SSI) and need to be activated manually.
Capability Name | Description | Supported System Type | Collection | Schedule Period |
---|---|---|---|---|
ABAP_WP_OVERVIEW | ABAP work process overview /SDF/SMON | ABAP | Agent (Push) | 1min |
HANA_THREAD_SAMPLES | HANA thread samples | HANADB | Agent (Push) | 1min |
HANA_MEMORY | HANA component memory consumption | HANADB | Agent (Push) | 5min |
HANA_LOAD_HOST | HANA Loadgraph per host | HANADB | Agent (Push) | 1min |
HANA_LOAD_SERVICE | HANA Loadgraph per service | HANADB | Agent (Push) | 1min |
HANA_EXPENSIVE_STATEMENTS | HANA expensive statements | HANADB | Agent (Push) | 5min |
HANA_TABLE_SIZE | HANA Table sizes | HANADB | Agent (Push) | 12h |
HANA_LONG_RUNNING_TRANSACTIONS | HANA Transactions active > 300s | HANADB | Agent (Push) | 5min |
Predefined Dashboards
For common system types pre-defined dashboards are delivered as part of the application. The subset of default dashboards actually shown in the list on the left side is filtered by the set of systems selected in the global scope selection. In addition, some dashboards are only shown and populated if corresponding data collectors are active for at least one system in scope. For example, HANA thread samples must be activated explicitly, and the page is only shown by default if the collection of HANA thread samples is active for one system in scope at the point in time when the global scope selection is done.
The catalog of all available dashboards is also available in the “Page Catalog” node of the left side navigation.
The following pre-defined default dashboards are available:
Name | Content | First Release | Notes |
---|---|---|---|
ABAP on SAP HANA | Combination of “ABAP Basis” and “SAP HANA | 1.0 FP03 | MAI-based |
ABAP Basis | SAP NetWeaver AS ABAP overview | 1.0 | MAI-based |
ABAP Exceptions | ABAP Exception details | 1.0 FP02 | EXM-based |
ABAP Performance | ST03-based data | 1.0 FP02 | ST03 data |
ABAP Work Processes | ABAP work process samples, drill down via guided RCA | 1.0 FP03 | Requires capability “ABAP_WP_OVERVIEW” |
SAP HANA | SAP HANA overview | 1.0 | MAI-based |
SAP HANA Component Memory | HANA memory details short-term and long-term | 2.0 SP00 | Requires capability “HANA_LOAD_SERVICE” |
SAP HANA Tables | HANA table statistics | 2.0 SP00 | Requires capability “HANA_TABLE_SIZE” |
SAP HANA Thread Samples | thread samples, drill down via guided RCA | 1.0 FP03 | Requires capabilities “HANA_THREAD_SAMPLES”, “HANA_EXPENSIVE_STATEMENTS” |
SAP HANA Expensive Statements | top expensive HANA statements | 1.0 | Requires capability “HANA_EXPENSIVE_STATEMENTS” |
SAP HANA Long Running Transactions | transactions that are active > 300 seconds | 4.0 | Requires capability “HANA_LONG_RUNNING_TRANSACTIONS" |
AS Java | SAP NetWeaver AS Java overview | 1.0 | MAI-based |
Business Objects | Business Objects Enterprise | 1.0 | MAI-based |
Data Services | Business Objects Data Services | 1.0 | MAI-based |
Apache Tomcat | 1.0 | MAI-based | |
ASE | SAP ASE data base overview | 1.0 | MAI-based |
Host | Basic OS-level metrics | 1.0 | MAI-based |
Java Exceptions | Exceptions for Netweaver Java Systems | 4.0 FP01 | EXM-based |
OS Process | operating system process snapshots | 4.0 FP02 | Requires capability "OS Process" |