This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
Java Agent version 0.7.x
editJava Agent version 0.7.x
edit0.7.0 - 2018/09/12
editBreaking changes
edit-
Removed
ElasticApm.startSpan
. Spans can now only be created from their transactions viaTransaction#createSpan
. -
ElasticApm.startTransaction
andTransaction#createSpan
don’t activate the transaction and spans and are thus not available viaElasticApm.activeTransaction
andElasticApm.activeSpan
.
Features
edit-
Public API
-
Add
Span#captureException
andTransaction#captureException
to public API.ElasticApm.captureException
is deprecated now. UseElasticApm.currentSpan().captureException(exception)
instead. -
Added
Transaction.getId
andSpan.getId
methods
-
Add
- Added support for async servlet requests
- Added support for Payara/Glassfish
- Incubating support for Apache HttpClient
- Support for Spring RestTemplate
-
Added configuration options
use_path_as_transaction_name
andurl_groups
, which allow to use the URL path as the transaction name. As that could contain path parameters, like/user/$userId
however, You can set theurl_groups
option to define a wildcard pattern, like/user/*
, to group those paths together. This is especially helpful when using an unsupported Servlet API-based framework. -
Support duration suffixes (
ms
,s
andm
) for duration configuration options. Not using the duration suffix logs out a deprecation warning and will not be supported in future versions. -
Add ability to add multiple APM server URLs, which enables client-side load balancing.
The configuration option
server_url
has been renamed toserver_urls
to reflect this change. However,server_url
still works for backwards compatibility. -
The configuration option
service_name
is now optional. It defaults to the main class name, the name of the executed jar file (removing the version number), or the application server name (for exampletomcat-application
). In a lot of cases, you will still want to set theservice_name
explicitly. But it helps getting started and seeing data easier, as there are no required configuration options anymore. In the future we will most likely determine more useful application names for Servlet API-based applications.