Splunk AppDynamics

Can Not See Expected MBeans

CommunityUser
Splunk Employee
Splunk Employee

We have the 4.3 Java Agent running in our IBM WebSphere Liberty server, and can see a lot of metrics already.

However the MBean Domain "WebSphere" does not show any entries.

We have followed the instructions in "Can Not See Excected MBeans", including the "last resort" step of setting the discover-mbeans property. This creates a directory und our <appagent>/conf directory, giving the nodename. Under that, we see an empty "discovered-mbeanservers" directory, but no "discovered-mbeans" directory.

Labels (1)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi @Anonymous

Please be advised that we have released Java Agent 4.5.4 with the following capabilities:

  • Certified to support WebSphere Liberty Profile.
  • Correctly interprets the new format of garbage collection and CPU consumption reporting introduced by IBM in the SR5 release of their Java SDK v8

 Product Update, November 2018 (v4.5.4) provides complete information on what's new in v4.5.4. 

Hope it's helpful.

0 Karma

Peter_Holditch
Builder

Benjamin,

WebSphere Liberty edition is currently not a certified platform.

If you look in the agent logs, you will see either permission or classloader errors relating to JMX access.

In other respects, the agent should function normally.

Warm regards,

Peter

0 Karma
Get Updates on the Splunk Community!

What’s New in Splunk Enterprise 9.4: Tools for Digital Resilience

What’s New in Splunk Enterprise 9.4: Tools for Digital ResilienceTune in to What’s New in Splunk Enterprise ...

Get Schooled with Splunk Education: Explore Our Latest Courses

At Splunk Education, we’re dedicated to providing incredible learning experiences that cater to every skill ...

Splunk AI Assistant for SPL | Key Use Cases to Unlock the Power of SPL

Splunk AI Assistant for SPL | Key Use Cases to Unlock the Power of SPL  The Splunk AI Assistant for SPL ...