Application Insights Java SDK 2.1.2

Welcome to Application Insights Java SDK 2.1.2 and Application Insights SpringBoot Starter 1.0.1-BETA! This release comes with some of the critical bug fixes both to our Spring-Boot starter and core SDK.

Enhancements:

1. Added timezone to internal SDK logger for better diagnostic ability of SDK.

Bug Fixes:

1. Fix #676 Fixes HTTP dependency collection issue with NetFlix Zuul library.
2. Fix #661 Shaded Guava package to avoid class path hell.
3. #685 Fixed potential security related bug - Disable DTD and external entities.
4. Fix #686 Added required attribute into the filter annotation
5. Fix #697 Fix persistent channel capability size.
6. Fix #691 Fixes cyclic reference issue in spring-boot starter.
7. Fix #711 Fixes a trailing whitespace in WebAppsHeartBeatProvider.

Application Insights Java SDK 2.1.1

Welcome to Application Insights Java SDK 2.1.1! With this version we announce ApplicationInsights-Spring-Boot-Starter-1.0.0-BETA. This starter is currently in BETA. In order to use SpringBoot starter please refer to https://github.com/Microsoft/ApplicationInsights-Java/blob/master/azure-application-insights-spring-boot-starter/README.md

Enhancement and API changes:

• Introducing support for SpringBoot via Application-Insights-SpringBoot-Starter #646. This is currently in beta.
• We have made some fields in core SDK public for supporting SpringBoot starter.
• Introduced public constructor in InProcessTelemetryChannel.java class.
• Introduced a public method getActiveWithoutInitializingConfig() in TelemetryConfiguration.java class.

Application Insights Java SDK 2.1.0

Welcome to Application Insights Java SDK 2.1.0! We have added support for heartbeats and made performance optimizations in the SDK's initialization code. A couple of other issues have also been fixed. See details below:

Enhancements:

• Introduced a Heartbeat feature, which sends periodic messages with basic information about application and runtime to Application Insights.
• Performance improvements during initialization.

Bug Fixes:

• Fixed an issue whereby the SDK could not resolve instrumentation keys if a proxy was specified in the JVM (via http.proxyHost). The fix enables proper support for system properties in the instrumentation key resolver component.
• Fix #647 - If a performance counter cannot be computed, it will not report a placeholder value (-1). Instead, it does not report any value.

Application Insights Java SDK 2.0.2

Welcome to Application Insights Java SDK 2.0.2! This release fixes a number of issues posted on GitHub by the community and ourselves. It also includes a few enhancements to diverse areas. Details below.

Note: This release requires that the SDK be run on an application server supporting Servlet 3.0 or above.

Enhancements:

• Enable real-time SDK Logs when logging to file - #616
• Log messages are now being pushed as custom dimensions when exceptions are reported via log appenders - #400
• Enhanced Log4j2 appender to support basic parameters including Filters, Layouts and includeException - #348
• Support for configuring channel retries (MaxInstantRetries) in ApplicationInsights.xml
• Added the ability to have cold SDK initialization (no logs except critical logAlways messages)
• Code cleanup in the session tracking feature - #577

Bug Fixes:

• Fix incorrect success flag set when capturing HTTP Dependency.
• Fixed issue with sessionId not being set in request telemetry due to date parsing incompatibilities.
• Fix #609, fixes the inaccurate timestamp recorded with JMX Metrics.
• Fix issue when dependency start time was not being recorded correctly.
• Fixed #533 HTTP Dependency Telemetry now matches with .NET SDK.
• Fixed PageView telemetry data not being reported.
• Fixed Issue #526 (NPE in MapUtil.copy()).
• Fixed Issue #513 (Memory leak in SDKShutdownActivity). This fix upgrades our Servlet version from 2.5 to 3.0. The SDK must now be run on an application server supporting Servlet 3.0.
• Fixed Issue #504 (SDK initialization happens twice) to improve startup performance.

API changes (back-compatible):

• Introduced public method httpMethodFinishedWithPath(String identifier, String method, String path, String correlationId, String uri, String target, int result, long delta)
  to support instrumentation of Path of URI in HTTP requests.
• httpMethodFinished(String identifier, String method, String correlationId, String uri, String target, int result, int delta) is now marked as deprecated

Application Insights Java SDK 2.0.1

This release patches an issue with 2.0.0 where Maven/Gradle users cannot add the SDK due to invalid POM files. issue #581

Application Insights Java SDK 2.0.0

Update: 2/28/2018 - NOTE for Maven/Gradle users: we have found an issue where you won't be able to use the SDK via Maven/Gradle. You might get an error message similar to this: "inconsistent module metadata found". See issue #581 for more details. We're currently working on a patch for this and we'll update this release notes once the patch is released. We apologize for any inconvenience.

Update 2: 2/28/2018 - The patch for the issue described above has been released. Thank you.

---

Welcome to the 2.0.0 (stable) release of the Application Insights Java SDK. With this release, we focused primarily on stabilizing the 2.0.0 Beta version, providing fixes to bugs affecting the reliability of the SDK. We have also conducted performance and stress tests in order to ensure the SDK’s overhead is minimal and does not negatively affect the performance of the host application.

Highlights:

• Upgraded logback dependency version to 1.2.3
• Improved FixedRateSampling so that it also supports Sampling Percentage set by users programmatically. Fixes issue #535
• Fault Tolerance improvements: introducing retries and exponential backoff capabilities with disk persistence.
• Retired support for Servlet 2.5. We now support Servlet 3.0+.
• Issue #499: Fix handling of NaN and +/-Infinity in JSON serializer
• Issue #506: Null Reference Check causing Null Pointer Exception in TelemetryCorrelationUtils.java

Application Insights Java SDK 2.0.0-BETA

• Introducing support for Cross-Component telemetry correlation (Supports Apache HTTP calls).
• Introducing Fixed Rate Sampling using Telemetry Processors (Recommended to use).
• Application Insights XML file can now be setted using SYSTEM PROPERTY - applicationinsights.configurationDirectory.
• Fixed Regression issue-Telemetry items with Severity level not being transmitted with SDK v1.0.10.
• Fixed dependency capturing issues of HTTP, Oracle SQL and MsSQL with JDK 1.8.
• Fixed Shadow Jar relocation issue (#276) . Prevents class path hell issues.
• Introduced Parameterized constructor to ensure SDK can be used smoothly with Spring Boot.
• Updating SDK dependencies in-order to latest versions to increase stability and security.
• Deprecating support for JDK 1.6. Enabling Application Insights would now require JDK 1.7 or above.
• Changed the signature of 'com.microsoft.applicationinsights.internal.agent.CoreAgentNotificationHandler.httpMethodFinished' to include correlation information.
• Introducing 'com.microsoft.applicationinsights.internal.channel.samplingV2.FixedRateSamplingTelemetryProcessor', Telemetry Processor for FixedRate Sampling.
• Introducing class 'com.microsoft.applicationinsights.internal.channel.samplingV2.SamplingScoreGeneratorV2'. Fixes the issues with some calculations for sampling.
• Adding two XML element classes : 'com.microsoft.applicationinsights.internal.config.ParamExcludedTypeXmlElement', 'com.microsoft.applicationinsights.internal.config.ParamIncludedTypeXmlElement' to support adding included and excluded types in the processor. This assists in FixedRateSampling V2 also.
• Introducing CustomClassWriter in Agent to enale finding avoid loading the actual class while instrumentation.

Application Insights Java SDK 1.0.10

1. Delay of 5 minutes in retrying to send failed requests.
2. Track() method in TelemetryClient fix to avoid overwriting provided telemetry timestamp.
3. Configurable instrumentation key via APPLICATION_INSTRUMENTATIONKEY envirornment variable.
4. Introduced a generic qualifer "Domain" which replaces "SendableData" as input to classes com.microsoft.applicationinsights.telemetry.BaseTelemetry
   and com.microsoft.applicationinsights.telemetry.BaseSampleSourceTelemetry.
5. Internal namespace "SendableData"is now deleted.
6. Schema is updated to latest version. Changes were made for internal namespace: com/src/main/java/com/microsoft/applicationinsights/internal/schemav2
7. Fixed reliability issue with Redis dependency collection.
8. Fixed issues sending telemetry with latest schema.
9. Fixed issue #403 - Exceeding property length invalidates custom event
10. Fixed issue #401 - Custom key and property sanitized
11. Addressed #429 - SDK now truncates fields according to new schema specs and performs proper sanitization
12. Method sanitization of interface com.microsoft.applicationinsights.telemetry.Telemetry is now Deprecated.
13. All Sanitization now occurs in one place - com.microsoft.applicationinsights.telemetry.JsonTelemetryDataSerializer class.
14. Sanitization only preformed when forming json to send telemetry. No presanitization is now done.
15. Dependency collection is in Beta*.

Currently open issues are : https://github.com/Microsoft/ApplicationInsights-Java/labels/bug , which includes all bugs found

Application Insights Java SDK 1.0.9

• Fixed #369 : Apache HttpClient 4.3.5 vulnerable (CVE-2015-5262)

Application Insights Java SDK 1.0.8

Listed below are the fixes and improvements made in 1.0.8

• #367 Updated the agent project not to be transitive when resolved for core
• #374 Updated the core JAR to remove the transitive dependencies for guava, removed the transitive dependency from core and agent, & updated to the latest version of the httpclient
• #376 Delaying retry on send when no connection is found
• #377 Bug fixes for Live Metrics Stream integration
• #378 Added Live Metrics Stream URL filter and fixed duration
• #379 Updated Gradle to 3.5
• #380 Delaying retry on send when ConnectionException is thrown
• #381 Delaying retry on send when HostUnknownException is thrown