Release 0.5.1

This release is a complete overhaul of the agent and makes it much easier to get started with. The agent now contains support for auto-instrumentation via -javaagent. You don't have to do any code changes in order to add the agent to your application. See the getting started guide how to add the -javaagent flag to your application.

New Features

• Improved performance. The performance has successfully been improved. The overhead is around 1.5 µs and 75 byte per request.
• The agent now supports the OpenTracing API via a bridge. See the OpenTracing documentation for more information.
• The agent filters sensitive information from HTTP headers and from data. See the configuration option sanitize_field_names for more information.

Migration from 0.1.2

Remove the dependency on co.elastic.apm:apm-agent-java and remove all manually registered interceptors: Remove the ApmFilter from web.xml, remove the Spring MVC ApmHandlerInterceptor and remove p6spy: in your JDBC URL.

If you have previously accessed the public API to customize the transactions and spans created by elastic APM or if you have manually created transactions and spans using the public API, you have to declare an explicit dependency to co.elastic.apm:apm-agent-api now. You also don't initialize ElasticApm with ElasticApm.get(), but you just call it's static methods instead. For example ElasticApm.startTransaction(). Be aware that the API is subject to change until version 1.0.0 is reached. See the docs of the public API for more information.

Release 0.1.2

This alpha version of the agent supports monitoring Spring Web MVC and Servlet API-based applications, including tracing of JDBC queries.

The alpha version does not, yet, support auto-instrumentation via -javaagent, so you have to integrate the Java agent manually. See the readme for more details.

Release 0.1.1

There are missing files on maven central for this release. Please use 0.1.2 instead