|
Note
|
For the best reading experience, please view this documentation at elastic.co |
The Elastic APM Java Agent automatically measures the performance of your application and tracks errors. It has built-in support for popular frameworks and technologies, as well as a simple API which allows you to instrument any application, and a Plugin API that allows you to add custom instrumentation.
|
Note
|
The minimum required version of the APM Server is 6.5.0 |
The Agent auto-instruments [supported-technologies] and records interesting events, like spans for database queries and transactions for incoming HTTP requests. To do this, it leverages the capability of the JVM to instrument the bytecode of classes. This means that for the supported technologies, there are no code changes required.
Spans are grouped in transactions — by default, one for each incoming HTTP request. But it’s possible to create custom transactions not associated with an HTTP request. Transactions and Spans are sent to the APM Server, where they’re converted to a format suitable for Elasticsearch. You can then use the APM app in Kibana to gain insight into latency issues and error culprits within your application.
More detailed information on how the Agent works can be found in the FAQ.
APM Agents work in conjunction with the {apm-guide-ref}/index.html[APM Server], {ref}/index.html[Elasticsearch], and {kibana-ref}/index.html[Kibana]. The {apm-guide-ref}/index.html[APM Guide] provides details on how these components work together, and provides a matrix outlining {apm-guide-ref}/agent-server-compatibility.html[Agent and Server compatibility].