Releases: microsoft/ApplicationInsights-Java
Application Insights Java 3.0.0 Preview
See 3.0 Preview: Getting started to get started with the 3.0 Preview release!
One of the major goals of the 3.0 Preview is to simplify the onboarding experience.
Adding the Application Insights Java SDK to your application is no longer required, as the 3.0 Preview agent auto-collects requests, dependencies, and logs all on its own.
But don't worry, it will still pick up custom telemetry that you send from your application, and the 3.0 Preview will track and correlate it along with all of the auto-collected telemetry.
Also new in 3.0 Preview is auto-instrumentation of several new libraries:
- JMS
- Kafka
- Netty/WebFlux
- Spring Scheduling
- Cassandra
- MongoDB async driver
- Redis Lettuce client
Application Insights Java SDK 2.6.0
Announcing Application Insights Java SDK 2.6.0!
There were no changes since 2.6.0-BETA.3.
Changes Since 2.5.0
Deprecations
If using Local Forwarder Channel, this will be a breaking change.
- Removed Local Forwarder Channel. Local Forwarder is now a deprecated solution.
The classes and configuration elements which supported this solution have been removed.
Enhancements
- Improved MongoDB instrumentation (#1132)
- W3C tracing with back-compat is now enabled by default (#1141)
- Use newer id format when reporting request and dependency telemetry (#1174)
- Removed unused dependencies from azure-application-ingishts-spring-boot-starter (xmlpull, xstream).
- Updated to the latest version of the struts API library (used by
com.microsoft.applicationinsights.web.struts.RequestNameInterceptor
). - Various stability improvements (#1177)
- Agent now supports Java 13 (#1149)
Bug Fixes
- Fixed memory leak with ChannelFetcher when TelemetryClient is instantiated in large numbers.
- Fixed
Unknown constant pool
issue with modeule-info.class when using older versions of ClassGraph. - Older Jersey versions failing when scanning classes due to inclusion of a few Java 8 class files (#1142)
- Fixed potential issue with URI building in ConnectionString parsing.
- Fix remote dependency target field format (#1138)
Application Insights Java SDK 2.6.0-BETA.3
Application Insights Java SDK 2.6.0-BETA.2
Announcing Application Insights Java SDK 2.6.0-BETA.2!
Deprecations
If using Local Forwarder Channel, this will be a breaking change.
- Removed Local Forwarder Channel. Local Forwarder is now a deprecated solution.
The classes and configuration elements which supported this solution have been removed.
Enhancements
- Removed unused dependencies from azure-application-ingishts-spring-boot-starter (xmlpull, xstream).
- Updated to the latest version of the struts API library (used by
com.microsoft.applicationinsights.web.struts.RequestNameInterceptor
). - Various stability improvements (#1177)
Bug Fixes
- Fixed
Unknown constant pool
issue with modeule-info.class when using older versions of ClassGraph. - Fixed potential issue with URI building in ConnectionString parsing.
- Fixed memory leak with ChannelFetcher when TelemetryClient is instantiated in large numbers.
Application Insights Java SDK 2.6.0-BETA
Application Insights Java SDK 2.5.1
Announcing Application Insights Java SDK 2.5.1!
There were no changes since 2.5.1-BETA.2.
Changes Since 2.5.0
Enhancements
- Connection String introduced for better government cloud support
- Agent now captures MongoDB queries
Bug Fixes
Application Insights Java SDK 2.5.1-BETA.2
Application Insights Java SDK 2.5.1-BETA
Introducing Application Insights Java SDK 2.5.1-BETA!
Enhancements
- Connection String introduced for better government cloud support
- Agent now captures MongoDB queries
Bug Fixes
- Fixed exception thrown by agent when using Apache HttpClient ResponseHandler methods (#1067)
Application Insights Java SDK 2.5.0
Announcing Application Insights Java SDK 2.5.0!
There were no changes since 2.5.0-BETA.5.
Summary of Changes Since 2.4.x
Enhancements
SDK-wide
- Added Java 9/10/11/12 support
- Introduced new jar,
applicationinsights-web-auto.jar
, which automatically registers the web filter. No need to modifyweb.xml
or add@WebFilter
. - Simplifies role name configuration by adding
<RoleName>
tag inApplicationInsights.xml
.
New Agent Features
- Generic JDBC driver support: captures JDBC queries for all JDBC drivers.
- Automatically captures dependencies for async requests by tracking the request across multiple threads.
- Agent now captures application logging from Log4j 2/1.2 and Logback.
- This removes the need to add the
applicationinsights-logging-*.jar
dependency and modify the application's logging configuration.
- This removes the need to add the
- Improved HTTP client support:
java.net.HttpURLConnection
- Apache HttpClient 3.x
- OkHttp3
- OkHttp2 now supports distributed tracing
- Sets
Operation Name
automatically based on Spring@RequestMapping
, JAX-RS@Path
and Struts action class/method name.- This removes the need for
RequestNameHandlerInterceptorAdapter
or other interceptors.
- This removes the need for
- Agent now supports multiple applications deployed in the same application server (temporarily in the 2.4.0)
- Simplified JBoss and Wildfly deployment when using the agent: no need for workarounds using
jboss.modules.system.pkgs
,java.util.logging.manager
,-Xbootclasspath
- Added agent logging capture threshold, configurable via
<Logging threshold="warn" />
in theAI-Agent.xml
, with default thresholdwarn
(#1026)
Removed/Deprecated
- Removed support for
<RuntimeException>
custom instrumentation inAI-Agent.xml
Bug Fixes
- #969 Fixes ability to configure Live Metrics iKey programatically.
- #978 Possible NPE during development
- Fixed request telemetry displaying
200
response code for some failed requests (#810) - Fixed GC performance counters not working (#929)
Miscellaneous
- Starting with this release, you can now find the agent and the collectd plugin on Maven Central as
applicationinsights-agent
andapplicationinsights-collectd
under the same group,com.microsoft.azure
.
Application Insights Java SDK 2.5.0-BETA.5
Introducing Application Insights Java SDK 2.5.0-BETA.5!
Bug Fixes
- Fixed
ClassCastException
that could happen when usingHttpURLConnection
(#1053)