Skip to end of metadata
Go to start of metadata

Overview

This page explains the IS Push service and how it is configured. It provides guidance how to troubleshoot problems and how to analyze grey metrics in System Monitoring of SAP Solution Manager and SAP Focused Run (FRUN).

General

The Introscope Push service (IS Push, also called SapPush) is a service running as part of the Introscope Enterprise Manager. The main goal of the IS Push is to send Introscope metrics to Solution Manager or SAP Focused Run Monitoring and Alerting Infrastructure (MAI). The IS Push is a service running as an Enterprise Manager plug-in, it is delivered as part of SAP Management Modules. Further information about the SAP Management Modules, check note 1579474.

The IS Push service starts when the Enterprise Manager is started and keeps running whilst the Enterprise Manager is running. Driven via XML configuration files that are transferred to the Introscope EM host via diagnostics agents the push service subscribes to Introscope metrics and pushes metric updates to the Monitoring and Alerting Infrastructure of Solution Manager and FRUN systems. The picture below describes a general overview about how the IS Push works.

It is possible to connect one Enterprise Manager to more than one SAP Solution Manager and more than one SAP Focused Run system at the same time. The Introscope Push service will then push metric updates to each of the connected Solution Manager / FRUN systems.

Configuration

The basic configuration of the Introscope Push is performed by activity 'Push DPC Configuration to Wily' of the Basic Configuration in SOLMAN_SETUP, the following picture describes where the activity can be found:


The activity 'Push DPC Configuration to Wily' creates the file <solman_SID>_e2emai.properties which is the main configuration file of the IS Push. This file is located in the EM installation path:

  • <EM install. dir.>/sap

The <solman_SID>_e2emai.properties holds the configuration of the resources required to run the IS Push. The main properties of this file are:

  • smdagent.name: Has the SMDAgent name of the Enterprise Manager host which is connected to the Solution Manager <solman_SID>;
  • metric.config.file: Has the location of file em.ISMetricCollectionDefinition.xml, details about em.ISMetricCollectionDefinition.xml can be found below;
  • dpcpush.credentials.file: Has the location of file em.Default_Configuration.properties, details about em.Default_Configuration.properties can be found below;

Configuration file em.ISMetricCollectionDefinition.xml: The file em.ISMetricCollectionDefinition.xml holds the metrics to be pushed to the Solution Manager Monitoring and Alerting Infrastructure. This file is located in the installation path of the SMDAgent specified in proprety smdagent.name of the <solman_SID>_e2emai.properties file. The location is:

  • {DiagnosticsAgentPath}/applications.config/com.sap.smd.agent.application.e2emai/MAI/

Configuration file em.Default_Configuration.properties: The file em.Default_Configuration.properties holds the credentials (user/pwd) required to call the DPC Push service in the Solution Manager system. This file is located in the installation path of the SMDAgent specified in proprety smdagent.name of the <solman_SID>_e2emai.properties file. The location is:

  • {DiagnosticsAgentPath}/applications.config/com.sap.smd.agent.application.e2emai/MAI/

Runtime Status

The Introscope Push runs as an extractor of the Alerting Framework, its runtime status can be found in the Alerting Framework application. The steps to access the Alerting Framework are:

  1. Transaction SM_WORKCENTER
  2. SAP Solution Manager Administration Workcenter
  3. Infrastructure
  4. Framework
  5. Alerting Framework

The Introscope Push extractor can be found searching for the extractors with the prefix 'IS_' in the Extended Context. Use a filter IS_* to find the Introscope Push related extractors. The following screenshot describes the Introscope Push in the Alerting Framework:

Runtime Log

The Introscope Push log file is the SapDpcPush.log, the file is located in the Enterprise Manager log folder, the location is:

  • <EM INSTALL PATH>\logs

In some, the file 'SapDpcPush.log' does not exist, e.g. because the diagnostics agent did not have write permission when "discovering" the Introscope EM in Solution Manager setup or because only FRUN systems are connected. In these cases the Introscope Push logs are written to the default IntroscopeEnterpriseManager.log. In these cases it is recommended to configure the Enterprise Manager to create the SapDpcPush.log. The procedure is described in note 1751225.

Troubleshooting

1. Introscope Push is not being executed

Symptom: In the Alerting Framework the Introscope Push extractor has 'Last Status' gray and the 'Last Update (UTC)' shows '00.00.000 00:00:0'. This indicates that the Introscope Push is not being executed by the Enterprise Manager. The following picture describes the issue:

Solution 1: 

Ensure that the SAP Management Modules have been installed in the Enterprise Manager, the section 'Install the SAP Management Modules' of the Introscope Enterprise Manager Setup Guide Shows how to perform the installation of the SAP Management Modules. This guide can be found at:

- http://service.sap.com/instguides - SAP Components - SAP Solution Manager - Release 7.1

Then execute the activity 'Push DPC Configuration to Wily' of the Basic Configuration in SOLMAN_SETUP to perform the basic configuration of the Introscope Push.

Solution 2:

If the IntroscopeEnterpriseManager.log shows the error 'Cannot read file DpcPushLib.jar from applications', check SAP KBA 2194893.

2. Introscope Push fails with error "No Web service configuration for this access path"

The SapDpcPush.log file shows the following error:

[EXCEPTION]
java.rmi.RemoteException: Service call exception; nested exception is:
java.lang.Exception: Call to {http://<Solution Manager host>:8000/sap/bc/srt/scs/sap/e2e_dpc_push?sap-client=600} returned http code 500 (SRT: Unexpected failure in SOAP processing occurred: ("No Web service configuration for this access path: "/sap/bc/srt/scs/sap/e2e_dpc_push?sap-client=600"")) with unacceptable content type (text/html).

Solution:

Refer to KBA 2210733 for the solution.

  • 2210733 - Introscope and DPC push are failing with a SOAP error: "No Web service configuration for this access path"

3. Introscope Push fails with error "The host of endpoint URL "https://host.my.domain:44389/sap/bc/srt/scs/sap/e2e_dpc_push?sap-client=200" was not found..."

The SapDpcPush.log file shows the following error:

[[ERROR] [Manager.SapPush.PS1] Push failed:

java.rmi.RemoteException: Service call exception; nested exception is: java.rmi.RemoteException: The host of endpoint URL "https://host.my.domain:44389/sap/bc/srt/scs/sap/e2e_dpc_push?sap-client=200" was not found. Check if the WS Client is configured correctly. Probably endpoint URL is not set or use of HTTP Proxy is required.; nested exception is: java.net.UnknownHostException: ldcisd7.wdf.sap.corp Caused by: java.rmi.RemoteException: The host of endpoint URL "https://host.my.domain:44389/sap/bc/srt/scs/sap/e2e_dpc_push?sap-client=200" was not found. Check if the WS Client is configured correctly. Probably endpoint URL is not set or use of HTTP Proxy is required.; nested exception is: java.net.UnknownHostException: ldcisd7.wdf.sap.corp

Caused by: java.net.UnknownHostException: host.my.domain

Solution:

Refer to KBA 2143416 for the solution.

2143416 - Introscope metrics are pushed to wrong Solution Manager URL 

4. Introscope Push fails with error "Problem loading file /usr/sap/<SID>/wilyintroscope/sap/<SID>.e2emai.properties
java.io.FileNotFoundException: sap/<SID>.e2emai.properties (The file access permissions do not allow the specified action.)"

The SapDpcPush.log file shows the following error:

9/02/16 04:48:31 PM CEST [INFO] [Manager.SapPush.<SID>] Reloading <SID>.e2emai.properties
9/02/16 04:48:31 PM CEST [ERROR] [Manager.SapPush.<SID>] Problem loading file /usr/sap/<SID>/wilyintroscope/sap/<SID>.e2emai.properties
java.io.FileNotFoundException: sap/<SID>.e2emai.properties (The file access permissions do not allow the specified action.)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at java.io.FileReader.<init>(FileReader.java:72)
at com.sap.introscope.em.push.PushConfiguration.loadFromFile(PushConfiguration.java:257)
at com.sap.introscope.em.push.PushConfiguration.checkIfUpdateRequired(PushConfiguration.java:273)
at com.sap.introscope.em.push.PushConfiguration.access$0(PushConfiguration.java:268)
at com.sap.introscope.em.push.PushConfiguration$1.run(PushConfiguration.java:75)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 

Solution:

Refer to KBA  2363559  for the solution.

2363559 - Introscope Push not working - monitoring metrics are gray

5. Introscope Push error "problem working with file /usr/sap/DAA/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.e2emai/MAI/em.ISMetricCollectionDefinition.xml
java.io.IOException: File is empty"

The SapDpcPush.log file shows the following error:

[ERROR] [Manager.SapPush.XXX] problem working with file /usr/sap/DAA/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.e2emai/MAI/em.ISMetricCollectionDefinition.xml
java.io.IOException: File is empty
at com.sap.introscope.em.push.mai.MaiMetricConfigManager.checkConfigFile(MaiMetricConfigManager.java:99)
at com.sap.introscope.em.push.mai.MaiMetricConfigManager.loadConfiguration(MaiMetricConfigManager.java:72)
at com.sap.introscope.em.push.mai.MaiMetricConfigManager.checkReloadMetricConfig(MaiMetricConfigManager.java:325)
at com.sap.introscope.em.push.mai.ConfigPoller$ConfigWatchRunnable.checkReloadConfiguration(ConfigPoller.java:39)
at com.sap.introscope.em.push.mai.ConfigPoller$ConfigWatchRunnable.run(ConfigPoller.java:51)
 

Solution:

In case you do not use System Monitoring you can ignore this log entry.

6. Introscope Self Monitoring metrics are flickering

The metric for Introscope Enterprise Manager Health is some times available and some times missing.

The SapDpcPush.log file shows the following entries:

 04:05:26 AM UTC [INFO] [Manager.SapPush.FRP] finished push to https://<host>/sap/srsm_mai/push_metrics  for 10000 metrics in 1491ms. Status=OK Status Message=httpStatusCode=200 responseBody=RC=0;METRICS=10000;ACCEPTED=10000;REJECTED=0;RUNTIME=1
 

Solution:

The number of metrics are limited by default to 10000. 

It can be increased be setting the property

alertqueue.max.entry.count=20000

in the file <EM install. Dir.>/sap/<SID>.e2emai.properties

Grey Metrics Troubleshooting


Important

For performance / response time metrics it may be normal that they are not present in the Investigator tree and/or that they appear sometimes as grey metrics in System Monitoring:

Introscope performance Metrics only show up when the measured functionality is executed for the first time. And if not executed for some time, the metric gets greyed out and disappears again from the tree. Of this metric then turns grey in System Monitoring. Furthermore, even if the metric is still active in Introscope, it may happen that no data point is reported to System Monitoring when the functionality has not been executed in the measurement interval: When a metric is available but there are no executions the count is 0 which might lead in System Monitoring to a grey metric.

Resource metrics like memory usage, thread usage should always be reported. If grey this must be analyzed.

Checklist

  1. Check if any historical data is available:
    1. In the System Monitoring UI, expand the tree to show the chart for the metric
    2. Click the calendar icon and choose a larger historical time range, e.g. 7 days
    3. If you see any data in this chart then this metric is working correctly. Probably it is a response time / performance metric. The behavior described in the box above applies. 
  2. Use the troubleshooting link is System Monitoring:
    1. Click on the metric name → a popup will open with summary information and some links
    2. Click "Check Data Collection" → The metric troubleshooting dialog will open 
    3. Check if the metric is provided by Introscope at all: Only if data provider is "PUSH_INTROSCOPE" the data is provided via Introscope. In all other cases: Forward to the right component! 
    4. Click on one of the tools links to navigate to the Alerting Directory Browser: The tab "Data Collection" shows the Introscope metric path at the very bottom of the page
  3. Now you know that the metric comes from Introscope - check on Introscope side
    1. Check if the Introscope EM is online
    2. Check if agent is online
    3. Check if the metric is available in the Introscope Investigator and reports data points.



  • No labels