Skip to Content

<p>Many Customer landscapes are very complicated and data collection for monitoring purposes is very extensive. Very often we can see below error in the logs

:</p><p> </p><p>Error<br />     com.sap.smd.wily.hostagent.action.IsProxyJCOAction$SchedulerGroup -<br />extractMetrics(): State RECORDED Dest<br />DE1CLNT970 SUSR_ZBV_GET_REMOTE_PROFILES:Oldest age(s)<br />[EXCEPTION]<br /> com.sap.smd.wily.hostagent.metric.MetricException: Metric Limit exceeded: 1000</p><p> </p><p>

The metric limitation 1000 is not enough for the SAPOSCOL action which is defined in the WilyHostAgentTemplate.xml. Simple solution would be to rise the limit to 2000 or 4000. To do so we need to follow below steps:</p><p> </p><p>1.) You could go to RCA workcenter -> Agent Administration -> application configuration.<br />Select com.sap.smd.agent.application.wilyhost -> Application Resources -> WilyHostAgentTemplate.xml in the left tree panel, download the standard one on the right top panel (please make a backup of this file that we can restore the default configuration if it will be necessary…).</p><p> </p><p>2.) Using text editor tool to modify that downloaded xml file.

Add XML attribute metriclimit=<your adjusted number, e.g. 1500> to action SAP OsCol like following:</p><p> </p><p>- <action prefix=”SAP OsCol” name=”SAPOsCol”<br />class=”com.sap.smd.wily.hostagent.action.SapOsColAction”<br />destination=”Process_Saposcol” period=”60000″ metriclimit=”2000″><br />   <property name=”sections” value=”CPU,Memory,Disks,Filesystems,LAN,MonitoredProcesses”><br />  </action></p><p> </p><p>3.) Upload it to the relevant Agent scope (DO NOT USE GLOBAL!!!!).</p><p> </p><p>4.) Restart that relevant SMD Agent to apply the new changes, check the SMD Agent application log to see whether that new threshold is still not enough.</p><p> </p><p>

You can also refer to the documentation “IntroscopeFAQ.pdf” attached in the SAP note 797147 and refer to point “7.8 Q” to increase the metric limit.</p><p> </p><p>In rare cases limit of 4000 still can be not big enough. In this case it is better to find out which function module generates such a extensive number of metrics rather than rise the limit even higher. To do that you need to run in target system report /SDF/ISPROXY_TEST which will allow you to see as a result which function module generates these thousands of metrics and maybe it can be limited.</p>

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply