The Java Agent monitors various Java Runtime Environments. It is loaded by a JVM at startup if configured to do so according the configuration set using a JVM command line option.
Please see Java Agent configuration to learn how to configure the Agent.
The Java Agent uses the following sensors:
|Management||JMX MBean Server|
|AMQP Receive Entry Point|
|JBoss ESB Tagging|
|JMS Receive Entry Point|
|MQSeries Receive Entry Point|
|Thread Start Tagging|
|Remoting||Remote Method Invocation (RMI)|
|Test Frameworks||Java Tests|
|Web Requests||Java Web requests|
|Web services||Java Web Services|
OneAgent released as BETA functionality for AppMon 2017 May. Please be aware that:
- Not all features/sensors available in Classic Agent are already available in the OneAgent for AppMon
- Features/Sensors known from Classic Agent can behave differently
To use OneAgent in AppMon 2017 May you need to install Classic Agents first, and then roll them out to the OneAgent. No additional configuration needed. Before you switch to OneAgent, double check your major requirements with the available feature set.
You must not use the OneAgent in your production environment. The aim of BETA is to test it in pre-production environment, and see how the new Agent affects your custom dashboards/configurations you use to monitor your production environment.
|Hot Sensor Placement|