About JavaProbe:

A Java runtime information-gathering tool which uses the Java Attach API for information acquisition (the related technical articles links are attached to the end of this article).

Instructions:

FAQ:

Q: Have you deployed JavaProbe in a production environment? 
A: Since 2017, it has been deployed on 90,000+ machines without any collateral damage.
The agent class logic is simple, and it will not damage the common business theoretically, but the JVM instance which will be hooked include agent class as residual, which is the current problem waiting to be solved. 

Q: What Java applications are supported by JavaProbe?
A: Common applications are supported, such as .war deployment and springboot .jar deployment, and so on.

Q: What data can we get with JavaProbe?  
A: virtual machine name, jdk version, classpath, run directory, temporary directory, running user, imported jar package, loaded class, etc.

Q: Why dose JavaProbe need the "root" privilege?
A: Because the JVMs with different user privilege are isolated and cannot be cross-permissions HOOKED, but root can use the runuser to run as different users to hook the user's own JVM instance.

Q: I still don't understand what can JavaProbe do?
A: 1.Check Java applications that use third-party components vulnerable (emergency response)
   2.Statistics of intranet Java applications status (fingerprint identification)
   3.Check legacy old vulnerabilities (time bombs) and development, which include high-risk services (like jolokia) (security baseline)

Example:

References:

Https://www.ibm.com/developerworks/cn/java/j-lo-jse61/index.html Java Instrumentation