DX Application Performance Management

Hi,

We have WebLogic 12.2.1.3.0 and are using Introscope agent (CA Wily Introscope(R) Version 10.5.2 Release 10.5.2.52).

When we look at the APM WebView under the managed server name, it display most metrics including Heap, etc, but the table were it says Threads in Use , it doesn't display any number just an empty graph. Yet on the same page you can do a live thread dump within APM WebView.

Is there something we are missing in the wily agent profile configuration?

The Threads in Use metrics are mapped by the ResourceMetricMap.properties file in the config folder of the Enterprise Manager

threads.used.path.2=WebLogic|JMX Aggregate|Thread Pool:Waiting Request Count

As per documentation, the JMX Aggregate metrics are generated by an extension that would have been present in the Enterprise Manager - .\ext\PPWebLogicExtensionPlugins.jar

https://docops.ca.com/ca-apm/10-2/en/implementing-agents/java-agent/java-agent-extensions/oracle-weblogic-server/installing-and-configuring-the-oracle-weblogic-server-extension/install-apm-for-oracle-weblogic-server/

this was part of the PowerPack for Weblogic which does not exist as a separate entity nowadays.

If you can find any other metric already reporting that could be relevant for you, you can update the ResourceMetricMap.properties file with reference to that file - most probably this would want to be sourced from JMX data, as the existing configuration indicates

This is just to point you hopefully towards the right direction, the only other thing I can say from our side is that we should review if there is any alternative default metric that could work.

Somewhat related, you can do thread tracing by using weblogic-full.pbl or if you have a typical pbl to uncomment ThreadTracing in toggles-typical.pbd by removing the #

# TurnOn: ThreadTracing

But ThreadTracing is the sort of thing that can cause performance and functionality issues in the app (which is why it goes in full instrumentation instead of typical) so it should be tested to see that it does not cause issues and also to review if it gives you something you really would need to have.

It would create a Threads node under the agent, I think you get a Current Threads In Use value out of there, you could then consider putting that metric in ResourceMetricMap.properties

Made this into a question. I marked the other post as duplicate -- https://communities.ca.com/message/242174028