Scribd
Upload
20 views14 pages

MAI Custom Is Metrics Part 2

Uploaded by

jaberyemeni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
20 views14 pages

MAI Custom Is Metrics Part 2

Uploaded by

jaberyemeni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

STEP 4: APPLIYING AND ACTIVATING THE MONITORING TEMPLATE

The last step is to apply your custom monitoring template to the managed object.
Assign Custom Templates to Managed Object
In SOLMAN_SETUP Technical Monitoring System Monitoring go to Step “Select Scope”. Select your
system in the system list.

Click Next. In the next step you have to make sure that you template containing the custom Introscope
metrics is assigned to your system. Click the “Assign Templates” link.

And assign the correct custom template.

Copyright/Trademark
Repeat this for all managed objects of this type (e.g. all instances) if necessary. After assigning the correct
template click on the “Apply and Activate” “All managed objects” button to activate your template.

Click Next and activate the reporting for the system if necessary.
Find the new Metrics in System Monitoring
Enter the System Monitoring application via transaction SM_WORKCENTER Technical Monitoring
System Monitoring. Select your managed system from the list and open the System Monitoring application.

Click on the system name to open the system hierarchy.

In the right area you find the metric viewer. Here you can navigate to your metric. Since we have created our
metrics in the J2EE instance template, we have to navigate to the instance and from there to the category of
out metric. We created two Performance metrics.

Copyright/Trademark
Example 1: Average Response Time (ms) of the SOAP Servlet

Example 2: Accumulated Response Time per interval (ms) for the VMC Top Method Statistics

Copyright/Trademark
APPENDIX: FURTHER EXAMPLES FOR CUSTOM METRICS
The following examples might seem to be a little bit made up, but they mainly intend to show what
possibilities you have by using different wildcard options in regular expressions.
Example 3: Processor Utilization % (aggregate)
The CPU utilization of processes (Java VMs) instrumented with the Introscope Netweaver agent.

At first we have to create a new data collector as a copy from the SAP data collector “Generic J2EE server
node data (Push)” as the metric is locked under the IS process SAP Netweaver.

Copyright/Trademark
Then we create a new metric and alert in the template management as described in this document before.

On the data collection tab you select your new data collector.

Copyright/Trademark
As PROC_NO you can enter the regular expression 1|11|13 to select only the processors 1, 11 and 13.

Enter thresholds and a technical name on the corresponding tabs.

And assign it to an alert (may you have to create a new one as described in this document before).

Copyright/Trademark
The result can be found in System Monitoring:

Copyright/Trademark
Example 4: Waiting tasks by Work Process type
The dispatcher queue reflects the number of tasks waiting for a work process. This number may increase
significantly during work process bottleneck situation.

This metric is very similar to the VMC Top Methods metric we created before. But since the VMC is not
active in all systems and hence the metric is not necessary available we decided to create another example,
which you can recreate in your own system.

Copyright/Trademark
The first step is again to create an own data collector. We can reuse the data collector “Generic Inst Data
WilyHost (Push)” which already contains the variables for SID and instance. Again we have to adjust the
parameters of the data collector.

Now we again create a new metric using our new data collector.

Copyright/Trademark
Assign a technical name to the metric and don’t forget to assign it to a custom alert.

Copyright/Trademark
The result can be found in the System Monitoring application.

Copyright/Trademark
TROUBLESHOOTING
Your custom metrics don’t appear in System Monitoring after activating the custom template
Solution: Most likely the Diagnostics agent in the Wily Introscope EM host is not running or connected to
Solution Manager. Hence the monitoring configuration cannot be transferred to Wily Introscope.
Check Diagnostics Agent on Wily Introscope EM host is up and running
Please make sure the Diagnostics agent running on the Introscope Enterprise Manager host is up and
running. If you run a MOM3 cluster make sure the Diagnostics agents on all collector hosts run as well.
To check to which Wily Introscope EM your system reports, go to the Managed System Configuration for
your system to Step “Enter System Parameters” and check the field “Introscope EM”

To check which Diagnostics agent is assigned to the Wily Introscope EM, go to Basic Configuration of SAP
Solution Manager to Step 3.1 “Configure CA Wily Introscope”, select the Wily Introscope from the list and
check the field “SMD Agent” and “Server Name” in the table below.

3
MOM = Manager of Managers. It’s a scalability solution for Wily Introscope EM, if the number of metrics
collected are too much for one stand-alone Introscope EM

Copyright/Trademark
To check if the Diagnostics agent is up and running and connected to SAP Solution Manager, please go to
the Diagnostics agent administration (http://<solman-host>:<solman-port>/smd/AgentAdmin) and search for
the agent (e.g. by server name).

Copyright/Trademark
Your custom metric appears in System Monitoring but stays grey
The first step is to check if the metric is available with a reasonable value in Wily Introscope. If not it’s highly
likely that the Diagnostics agents for the managed system are shut down. They have to be restarted.
If the metrics are valid in Wily Introscope but do not appear in system monitoring you should check if the
Diagnostics agents for the managed system are also properly connected to SAP Solution Manager.
You can do this in the Agent Administration application.

In some rare cases the agents could be running, but cannot connect to Solution Manager because of invalid
credentials. As of SP 05 there is a new tab in the Agent Administration for these agents, the tab Non-
authenticated Agents.

Reconnect the diagnostics agents of the managed system properly.


After reconnecting you have to rerun the step “Apply and activate” the custom templates4.

4
Especially if you add metrics which are located under the IS process SAP HostAgent you need the SMD
agents of the managed system up and connected during the activation of the custom template. The SMD
agent instance name is used in the IS_PROCESS_NAME variable and this one is generated on activation.
When the agent is down or not connected to Solution Manager the wrong path is generated and stored in the
configuration file and the metrics will not be delivered.

Copyright/Trademark

You might also like