data-accelerator
data-accelerator copied to clipboard
Bump applicationinsights-core from 2.6.4 to 3.4.0 in /DataProcessing/datax-utility
Bumps applicationinsights-core from 2.6.4 to 3.4.0.
Release notes
Sourced from applicationinsights-core's releases.
Application Insights Java 3.4.0 (GA)
(Also see what was included in 3.4.0-BETA.)
Enhancements:
- Introduce a new preview feature: Java Profiler for Azure Monitor Application Insights
- Update OpenTelemetry to 1.18.0 #2509.
- Remove limit on filtering default metrics #2490.
- Add a new config to export logback code attributes #2518
Application Insights Java 3.4.0-BETA
Migration notes:
- Rate-limited sampling is the new default. If you have not configured a sampling percentage and are using the prior default behavior of 100%, you will get the new default which limits the total requests captured to (approximately) 5 requests per second (along with their dependencies, traces and custom events). If you wish to continue with the previous behavior, you can explicitly specify a sampling percentage of 100, e.g.
{ "sampling": { "percentage": 100 } }Enhancements:
- Standard metrics for HTTP requests and HTTP dependencies are now pre-aggregated inside of the Java agent, and so they are no longer affected by sampling (#2439).
- Rate-limited sampling has been introduced which can be used to tune ingestion costs (#2456), e.g.
Note: the{ "sampling": { "limitPerSecond": 5 } }limitPerSecondcan be a decimal value, including values less than 1.- Exceptions are no longer captured directly on dependency records for these reasons:
- in order to reduce ingestion cost
- dependency exceptions which are uncaught, bubble up to the request-level where they are already captured
- dependency exceptions which are caught, tend to be logged if they are important, where they are also already captured (#2423).
- New versions of the
applicationinsights-coreandapplicationinsights-web2.x SDK artifacts have been released, with a reduced API surface area to makes it clear which APIs interop with the 3.x Java agent (#2418). These new versions are no-ops when run without the Java agent. To update your dependencies:
2.x dependency Action Remarks applicationinsights-coreUpdate the version to 3.4.0-BETAor laterapplicationinsights-webUpdate the version to 3.4.0-BETAor later, and remove the Application Insights web filter yourweb.xmlfile.applicationinsights-web-autoReplace with 3.4.0-BETAor later ofapplicationinsights-webapplicationinsights-logging-log4j1_2Remove the dependency and remove the Application Insights appender from your log4j configuration. This is no longer needed since Log4j 1.2 is auto-instrumented in the 3.x Javaagent. applicationinsights-logging-log4j2Remove the dependency and remove the Application Insights appender from your log4j configuration. This is no longer needed since Log4j 2 is auto-instrumented in the 3.x Javaagent. applicationinsights-logging-log4j1_2Remove the dependency and remove the Application Insights appender from your logback configuration. This is no longer needed since Logback is auto-instrumented in the 3.x Javaagent. applicationinsights-spring-boot-starterReplace with 3.4.0-BETAor later ofapplicationinsights-webThe cloud role name will no longer default to spring.application.name, see the 3.x configuration docs for configuring the cloud role name.
... (truncated)
Changelog
Sourced from applicationinsights-core's changelog.
Version 3.4.0 GA
- Introduce a new preview feature: Java Profiler for Azure Monitor Application Insights
- Update OpenTelemetry to 1.18.0 2509.
- Remove limit on filtering default metrics 2490.
- Add a new config to export logback code attributes 2518.
Version 3.4.0-BETA.2
Migration notes:
- If you were using Automatic naming before, you will need to update your module-info.java file. Change
requires applicationinsights.runtime.attach;torequires com.microsoft.applicationinsights.runtime.attach;and everything should work.Enhancements:
- Automatic module name entry added to Runtime Attach library Jar to support Modular Java.
Version 3.4.0-BETA
Migration notes:
- Rate-limited sampling is the new default. If you have not configured a sampling percentage and are using the prior default behavior of 100%, you will get the new default which limits the total requests captured to (approximately) 5 requests per second. If you wish to continue with the previous behavior, you can explicitly specify a sampling percentage of 100, e.g.
{ "sampling": { "percentage": 100 } }- Both percentage-based and rate-limited sampling now only apply to requests, and to telemetry that is captured in the context of a request. If you do want to sample "standalone" telemetry (e.g. startup logs), you can use sampling overrides, e.g.
{ "preview": { "sampling": { "overrides": [ { "telemetryType": "dependency", "includingStandaloneTelemetry": true, "percentage": 10 } ] }
... (truncated)
Commits
bc353f0Add synthetic metric dimension smoke test (#2528)3b36f75Add smoke test for preagg metrics with sampling and overrides enabled (#2521)96f1e9fRelease 3.4.0 (#2527)661d471Update standalone sampling behavior (#2526)1defa04pre-agg + override + sampling (#2523)8542a6bMove unsign tool to applicationinsights-java-tools repo (#2525)f3bca04Option to export logback code attributes (#2518)24d4857Update to otel 1.18.0 (#2509)5c2cdbaBump version for upcoming release (#2520)269a8ceFix sampling for custom instrumentation (#2513)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)