Getting Data In

Java JMX MBean ObjectName

faguilar
Path Finder

Hi Splunkers!

I'm having trouble with the Splunk JMX App. I used to work with version 3.0.2 but I needed to make an update to the current version 3.1.0 due to my clients' needs. The thing is that, I had a lot of dashboards using tags for the values of the previous 3.0.2 version for the field source, like:

source=service:jmx:rmi://myhost1/jndi/rmi://myhost1:port/jmxrmi
source=service:jmx:rmi://myhost2/jndi/rmi://myhost2:port/jmxrmi

And, since the update, as pointed out here: http://docs.splunk.com/Documentation/AddOns/released/JMX/Releasehistory#New_Features, now the source field from JMX connection string (e.g., service:jmx:rmi:///jindi/rmi://127.0.0.1:8888/jmxrmi) has changed to to JMX MBean ObjectName (e.g., kafka.server.ReplicaManager.UnderReplicatedPartitions).
So, now, my source fields are like this:

source=java.lang:type=Memory
source=java.lang:type=OperatingSystem

And my dashboards doesn't show info anymore, since I'm using the tags for that previous values of source, like "Area1" for myhost2, "Area2" for myhost2 and so on. I need to recover this, because there are like A LOT of monitoring info from A LOT of computers.

So, my main question here is: Is there a way to "recover" in the current 3.1.0 version, the values of the source field like in the previous 3.0.2 version?? Or maybe there are still there but in another java bean or property and I need to configure de JMX sourcetype to take those values in the xml conf??
Is this possible or is a matter of the app and the development and it can't be changed anymore??

Thank you very much!

Tags (5)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...