The two data collection agents
The two collection agents...
- ARM agent
Most useful, and will be selected automatically, when...
- Analyzing Java EE applications, especially in distributed applications where event correlation is essential.
- Profiling ARM-instrumented applications.
For example, if you ARM-enable a database, you could view a transaction go from application into the database, see all the processing in the database, and then see the response return, all displayed in one sequence diagram.
- Using a shared server, to profile transactions only while filtering out all other server activity.
- JVMPI agent
Most useful, and will be selected automatically, when...
- Performing garbage collection and memory leak analysis.
- Examining object interactions, for example, UML2 Object Interactions view.
In most situations, class interaction analysis (available with the ARM agent) is enough to help find problems, but occasionally you will need to do further profiling at the object level.
- Profiling non-Java EE Java applications, such as Java SE or Java ME applications.
Each agent offers its own set of data collection features...
Feature: ARM agent JVMPI agent Correlate remote calls between processes and hosts Yes No Performance hit when agent runs in profiling mode Small effect Large effect Filtering mechanisms Java EE component type servlet
JDBC
...Host URL
package
class
methodCollect information for UML2 Object Interactions No Yes