-
Request for existing cases, user IDs, Portal navigation support and more
System Analysis
Detailed monitoring and analysis of a small group of systems
Request for existing cases, user IDs, Portal navigation support and more
Detailed monitoring and analysis of a small group of systems
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.
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.
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. |
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 |
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" |
Tabular data display: Toggle data display between chart and table
"Technical Details" in Tools menu displays details on configured metrics and scope
Page Catalog listing all predefined pages
Cope with duplicate metrics, e.g. same technical metric name from different templates for same system
Improved number formatting: reduce decimal digits for large numbers
Stable color assignment to systems / metrics cross views
UI5 cache buster activated to enforce automated browser cache refresh in case of updates
Improved time zone support: Aggregation to daily values now considers the browser time zone
Suppress click-tooltip for "Guided RCA" pages (ABAP WP Mon, HANA Thread Samples)
Creatable view types are grouped by category (data source type): MAI, RCA, Statragg, etc.
Personalizable links for views and pages (web, page, FRUN application)
Personalizable selection propagation (Guided RCA)
automated chart type adjustment for "no time axis" resolution
New chart option "show markers" to display data points. This helps to reveal "isolated" data points in charts with gaps
Metric catalog: new search function
Scaling of metrics
HANA Component Memory
HANA Table Sizes
HANA Statements
HANA Expensive Statements
HANA Load Host
HANA Load Services
System Monitoring Setup of the Technical Systems involved is required for the default dashboards to be populated
For basic usage of System Analysis no dedicated setup steps are necessary. All systems for which System Monitoring is configured should automatically also work in System Analysis.
The System Analysis aggregated store allows to retain selected metric data from the MAI store beyond the standard retention time of the MAI store. The content of the aggregate store is defined based on variants. Using these variants a daily task collects and aggregates data from the MAI store and persists it in a dedicated store.
For each variant you can define
The retention period (in days): After this period data will be eliminated from the aggregate store
The look-back time (in days): This is the overlap of the MAI store with the aggregate store. For a MAI store retention time of 28 days and a look-back time of 2 days the aggregation task will gather data that is 26 days old.
The aggregation granularity: You can choose between 5 minutes, 15 minutes, hourly, and daily granularity. Choose you appropriate compromise between granularity and space consumption.
Customer networks: You can restrict variants to selected customer networks
Data store: “Standard Aggregate Table Store” is the only option supported for consumption in the System Analysis application.
Systems: You can specify various filter criteria to select for which systems data aggregation should take place at all
Metrics: You can select metric categories and individual metric names for aggregation
Note that there is no mechanism to automatically detect and warn about overlap between variants. Technically it is possible to capture the same metrics for the same systems in different variants. Make sure to carefully tailor the variants for your needs. The “Calculate Duplicates” button allows to estimate overlap of a variant with all others. You can also decide to intentionally collect identical metrics in different variants, e.g. with a daily granularity for a long retention period and in addition with a finer granularity with a stricter retention policy.
Starting with SAP Focused Run 2.0 FP03 RCA capabilities can be activated automatically by SSI depending on LMDB attributes. See details on page Activation of RCA Capabilities. As pre-requisite the aggregate performance data must be available e.g. in transaction ST03N in the managed system. A typical source for missing data is that the corresponding aggregation job is not active in the managed system. See SAP Note 2369736 for troubleshooting missing data in ST03N. The “related links” in the System Analysis application points to the “ABAP Performance KPI Setup” application. Here you can explicitly select the instance to use for data collection and check the collection status.
Starting with SAP Focused Run 3.0 FP03 a new view for Database connections is available. If this should be displayed in System Analysis an additional configuration needs to be added to collect this data.
In SE16 create or update for table STATRAGG_CFG the value for this entry:
TYPE COLLECTOR
PARAM EXTRA_TABLES
VALUE DBCON
If SSI is executed the next time a new configuration is send to the agent and with next STATRAGG collection (one day later) data is sent to FRUN.
All data collectors for root cause analysis capabilities beyond standard system monitoring metrics can be controlled directly in the System Analysis application. Use the gear button () to open the configuration for all systems in the current scope selection. For each system there is a drop-down list of available capabilities. Activate the desired capabilities and click save to trigger immediate activation.
To get a tabular overview on active capabilities, especially for a larger set of systems, there is a "table" button in the header section of the System Settings panel. You get a tabular presentation for all selected systems and all capabilities. The system selection can be overridden in this table (to select more than ten systems), capability activation can be directly changed in the table, and download from this table is also possible.
Starting with SAP Focused Run 2.0 FP03 RCA capabilities can be activated automatically by SSI depending on LMDB attributes. Since SAP Focused Run 3.0 SP00 you can as well activate the collection of ABAP exceptions by setting the capability ABAP_EXCEPTIONS_ALL. This collection collected is performed by Exception Monitoring. See details on page Activation of RCA Capabilities.
ABAP_WP_OVERVIEW
You can activate /SDF/SMON in the managed system from within System Analysis via the configuration . If an analysis is already scheduled in the managed system by another user the existing scheduling is not changed. Requirement for this capability is ST-PI 7.40 SP08 in managed system.
Following details can be scheduled for analysis in managed system additionally:
SM04 = Memory per (user) modes
ST06 = CPU and paging activity
TOPCPU = Top CPU processes
These non-default flags have a higher impact on the managed system and the data is not collected and transferred to SAP Focused Run but only helpful for local analysis in managed system.
In the managed system the batch jobs /SDF/SMON_SCHEDULER and /SDF/SMON_WATCHDOG are scheduled which are responsible for the local measurement.
HANA SQL scripts
To use the RCA capabilities for system type HANADB you may have to copy the scripts from SAP Note 2555664 (Enable HANA Dashboards and Ad-Hoc SQLs in System Analytics for Focused Run) to all host agents of your HANA databases. The note lists in detail for which combinations of diagnostics agent version and SAP Host Agent version manual activities are necessary.
HANA Expensive Statements
To collect the expensive statements from the HANA DB they need to be enabled in the HANA database first. See also https://help.sap.com/viewer/bed8c14f9f024763b0777aa72b5436f6/2.0.03/en-US/5faf04f17830464eacdb7938b383d2ab.html or the FAQs in SAP Note 2180165 FAQ: SAP HANA Expensive Statements Trace.
SAP Cloud Platform Metrics
To enable the collector for SAP Cloud Platform (Neo) metrics an external service with the required http endpoint and root URL needs to be created.
Open the Cloud Service Management Configuration and add an external service of type SAP Cloud Platform (Neo) for your account with the root URL https://api.hana.ondemand.com. Create an endpoint with your user and a proxy if required.
When launching System Analysis either from the SAP Focused Run launchpad or via an explicit link you will first receive a popup to choose a set of systems to look at. By default, the number of systems to be displayed in System Analysis is limited to a maximum of ten (see FAQ section to raise the limit and to avoid the initial scope selection). If you choose more than ten systems in the bottom table of the scope selection, then the first ten will be chosen.
After finishing the scope selection, the System Analysis application comes up with the typical layout common to most Focused Run applications:
The header bar contains a set of global tools:
The list of pages (dashboards) on the left side will be populated with default pages (based on selected system types), the page catalog, and custom pages.
The page toolbar serves as overview and selection tool for the content of the page. It consists of the following main sections:
Every single view provides the following functionality. Depending on the capabilities and data sources consumed not all aspects will be available for all views.
The following options are available via the View title bar:
There are currently two pre-defined dashboards that provide built-in drilldown into performance data: ABAP Work Processes and HANA Thread Samples. The idea is that selecting a data point in a chart (by clicking on it) serves as filter criteria for the subsequent chart. As a concrete example for ABAP Work Processes the following might be a useful workflow:
The Guided RCA approach can also be applied to custom dashboards, e.g. by copying a predefined dashboard and adjusting the “Selection Propagation” settings in the view personalization.
You can create custom dashboards by copying existing dashboards or by starting via the “Add Page” functions in the left-side navigation or in the personalization. The mechanisms are basically like all other Focused Run applications, thus only application specific details are explained here.
Placeholder | Description |
---|---|
{SYSTEM.ExtendedSID} | Extended sid, e.g. FRNADM |
{SYSTEM.SID} | Short 3-letter System ID, e.g. FRN |
{SYSTEM.SystemType} | System type like “ABAP”, “JAVA” |
{SYSTEM.NamespaceName} | CIM namespace name |
{SYSTEM.LMDBID} | LMDB guid (32 char notation) |
{HOST.LMDBID} | LMDB guid (32 char notation) |
{HOST.NAME} | Unqualified host name |
Every capability's data base table will be cleaned up and partitioned by the housekeeping job SAP_FRN_RCA_HOUSEKEEPER which is part of the SAP Focused Run installation guide. The lifespan of the RCA capabilities tables can be customized on the SM30 view RCA_HKCONFIG. See also the System Analysis Housekeeping page for default values.
The housekeeper also manages several jobs related to System Analysis and the RCA data stores. The periodicity of these jobs can be customized on the SM30 view RCA_HKJOBLIST:
the HANA statement synchronization job SAP_FRN_RCA_HANA_STATEMENT_SYNC which will synchronize HANA statements used by the RCA application, as well as the jobs SAP_FRN_RCA_SELFMON_CALC and SAP_FRN_RCA_GS_ALERT_CALC. Both calculate alerts for the RCA self-monitoring and Open KPI Store. The default frequency is once per hour.
The job SAP_FRN_RCA_ORPHAN_DETECTION detects and eliminates orphaned collector jobs (e.g. due to landscape changes) and runs once per day by default.
Hints for troubleshooting are described on page System Analysis Troubleshooting.