opentelimetry configuration with JMX metrics in grafana dashboard.

[Sam829-i]

Complexity of Setup: Configuring OpenTelemetry to collect JMX metrics can be complex, involving multiple steps and configuration files. You might find it challenging to understand all the required parameters and settings.
I have updated my yaml file with the mbeans but still my metrics is not visible.

What should I do now?

[Sam829-i]

@PeterF778 could you please help? It would be great.

[PeterF778]

Did you try debug logging? Use -Dotel.javaagent.debug=true and capture the stderr output. There will be a lot of messages, but you should be able to filter them out easily.

[Sam829-i]

yes I have tried to add the debug argumanets. The error I have recived

class load: io.opentelemetry.javaagent.shaded.instrumentation.jmx.engine.MetricInfo$Type from: file:/D:/ELK/opentelemetry/jmx-opentelemetry-javaagent.jar
class load: io.opentelemetry.javaagent.shaded.instrumentation.jmx.engine.MetricAttributeExtractor from: file:/D:/ELK/opentelemetry/jmx-opentelemetry-javaagent.jar
class load: io.opentelemetry.javaagent.shaded.instrumentation.jmx.engine.BeanAttributeExtractor from: file:/D:/ELK/opentelemetry/jmx-opentelemetry-javaagent.jar
class load: javax/management/InstanceNotFoundException from: D:\APP\WebSphere\AppServer\java\8.0\jre\lib\rt.jar
class load: io.opentelemetry.javaagent.shaded.instrumentation.jmx.engine.BeanAttributeExtractor$1 from: file:/D:/ELK/opentelemetry/jmx-opentelemetry-javaagent.jar
class load: io.opentelemetry.javaagent.shaded.instrumentation.jmx.engine.BeanAttributeExtractor$2 from: file:/D:/ELK/opentelemetry/jmx-opentelemetry-javaagent.jar
[otel.javaagent 2025-05-28 14:59:03:573 +0200] [main] INFO io.opentelemetry.javaagent.shaded.instrumentation.jmx.yaml.RuleParser - D:\ELK\opentelemetry\simplifiedDemo.yml: found 2 metric rules

Iam using Grafana for visualisation and I could see only artiom26 metrics but not the JMX metrics.

The yaml file I am using marked x for some security reason I wont be able to paste here

rules:

• bean: java.lang:type=Memory
  mapping:
  HeapMemoryUsage.used:
  metric: artiom26.jvm.memory.heap.used
  type: gauge
  desc: Used heap memory
  unit: bytes
  HeapMemoryUsage.committed:
  metric: artiom26.jvm.memory.heap.committed
  type: gauge
  desc: Committed heap memory
  unit: bytes
  HeapMemoryUsage.max:
  metric: artiom26.jvm.memory.heap.max
  type: gauge
  desc: Maximum heap memory
  unit: bytes

• bean: WebSphere:name=xxxx,process=SystServer01,platform=xxx,node=SystNode01,version=9.0.5.16,type=ListenerPort,mbeanIdentifier=cells/SYST/nodes/SystNode/server.xml#ListenerPort_xxxx,cell=SYST,spec=1.0
  mapping:
  started:
  metric: demo.started
  unit: boolean

[Sam829-i]

I am using Websphere application version 9.0.5.16

[jkwatson]

I believe this issue belongs in the instrumentation repo. Is it ok if I move it there?

[Sam829-i]

Yes sure you can

[PeterF778]

I guess there were no other warnings/errors in the debug log (?).
Possibly there is an issue with MBean permissions. Do you see the MBeans you want using jconsole?

[Sam829-i]

yes tehre is no other warnings except those.
I tried to access jconsole but to access I tried to add the Java virtual machine paramenters -Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=8686 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false but after adding those parameters my JVM is not coming up or its not supporting. Any idea how I can access jconsole?

[PeterF778]

I presume you are using IBM J9 JVM which typically comes with WebSphere, but even such JVM should support jconsole. See https://www.ibm.com/docs/en/sdk-java-technology/8?topic=reference-using-jconsole
If the JVM does not come up, there should be some errors logged - what are they?

[Sam829-i]

there is no particular error message why the JVMs is unable to start. I tried for jconsole its not working.

[Sam829-i]

WebSphere is running as a node (seaparate service)

[Sam829-i]

I was trying to use WSADMIN so got few outputs on JMX listner ports

wsadmin>print mbeans
WebSphere:name=xxxxx,process=WServer01,platform=xy,node=SystNode01,version=9.0.5.16,type=ListenerPort,mbeanIdentifier=cells/SYST/nodes/Node/servers/WServer01/server.xml#ListenerPort_xxxxxx,cell=SYST,spec=1.0