search

cloudcaptainsh / cloudcaptain

Issue Tracker for CloudCaptain
13 stars 3 forks source link

Scant JMX information JDK 17 #274

Closed knocknarea closed 1 year ago

knocknarea commented 1 year ago

@axelfontaine Not sure if this is the amd64 instance or the currently latest version (available through cloudcaptain inventory)

But there is no CPU information (or GC aggregated statistics) available via JMX/JMC.

See the difference between local (JDK 17.0.4) and remote (JDK 17+35 - cloudcaptain instance on AWS)

JDK 17.0.4

Screenshot 2022-10-21 at 09 44 15

Cloudcaptain Instance

Screenshot 2022-10-21 at 09 43 57

It's very difficult to analyze the application in terms of tying everything to the CPU/Load, etc.

Screenshot 2022-10-21 at 09 54 05

I wonder is it the version of JDK used by cloud captain or is it related to the AMI?

axelfontaine commented 1 year ago

This is most likely due to our trimmed view of /proc and /sys. We'll look at correcting this in the future. No ETA promises though.

knocknarea commented 1 year ago

@axelfontaine Appears to be working OK since OpenJDK 17.0.5. Thank you