Application Insights for Java
OTHER License
Bot releases are hidden (Show)
Published by heyams 8 months ago
Published by heyams almost 2 years ago
Published by heyams about 2 years ago
Published by heyams about 2 years ago
Published by heyams about 2 years ago
{
"sampling": {
"requestsPerSecond": 5
}
}
Note: the requestsPerSecond
can be a decimal value, including values less than 1.applicationinsights-core
and applicationinsights-web
2.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-core |
Update the version to 3.4.0-BETA or later |
|
applicationinsights-web |
Update the version to 3.4.0-BETA or later, and remove the Application Insights web filter your web.xml file. |
|
applicationinsights-web-auto |
Replace with 3.4.0-BETA or later of applicationinsights-web
|
|
applicationinsights-logging-log4j1_2 |
Remove 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-log4j2 |
Remove 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_2 |
Remove 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-starter |
Replace with 3.4.0-BETA or later of applicationinsights-web
|
The cloud role name will no longer default to spring.application.name , see the 3.x configuration docs for configuring the cloud role name. |
{
"preview": {
"connectionStringOverrides": [
{
"httpPathPrefix": "/myapp1",
"connectionString": "InstrumentationKey=12345678-0000-0000-0000-0FEEDDADBEEF;IngestionEndpoint=...;..."
},
{
"httpPathPrefix": "/myapp2",
"connectionString": "InstrumentationKey=87654321-0000-0000-0000-0FEEDDADBEEF;IngestionEndpoint=...;..."
}
]
}
}
{
"instrumentation": {
"jdbc": {
"masking": {
"enabled": false
}
}
}
}
{
"preview": {
"sampling": {
"overrides": [
{
"telemetryKind": "dependency",
...
"percentage": 0
}
]
}
}
}
applicationinsights-core
artifact (#2447).operation_Id
and operation_parentID
being captured as 00000000000000000000000000000000
for "standalone" log records (which occur outside of a request). These fields are now empty for "standalone" log records, to reflect that they are not part of an "operation" (i.e. request) #2432.Published by heyams about 2 years ago
{
"sampling": {
"percentage": 100
}
}
{
"sampling": {
"requestsPerSecond": 5
}
}
Note: the requestsPerSecond
can be a decimal value, including values less than 1.applicationinsights-core
and applicationinsights-web
2.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-core |
Update the version to 3.4.0-BETA or later |
|
applicationinsights-web |
Update the version to 3.4.0-BETA or later, and remove the Application Insights web filter your web.xml file. |
|
applicationinsights-web-auto |
Replace with 3.4.0-BETA or later of applicationinsights-web
|
|
applicationinsights-logging-log4j1_2 |
Remove 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-log4j2 |
Remove 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_2 |
Remove 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-starter |
Replace with 3.4.0-BETA or later of applicationinsights-web
|
The cloud role name will no longer default to spring.application.name , see the 3.x configuration docs for configuring the cloud role name. |
{
"preview": {
"connectionStringOverrides": [
{
"httpPathPrefix": "/myapp1",
"connectionString": "InstrumentationKey=12345678-0000-0000-0000-0FEEDDADBEEF;IngestionEndpoint=...;..."
},
{
"httpPathPrefix": "/myapp2",
"connectionString": "InstrumentationKey=87654321-0000-0000-0000-0FEEDDADBEEF;IngestionEndpoint=...;..."
}
]
}
}
{
"instrumentation": {
"jdbc": {
"masking": {
"enabled": false
}
}
}
}
{
"preview": {
"sampling": {
"overrides": [
{
"telemetryKind": "dependency",
...
"percentage": 0
}
]
}
}
}
applicationinsights-core
artifact (#2447).operation_Id
and operation_parentID
being captured as 00000000000000000000000000000000
for "standalone" log records (which occur outside of a request). These fields are now empty for "standalone" log records, to reflect that they are not part of an "operation" (i.e. request) #2432.Published by heyams about 2 years ago
Published by heyams over 2 years ago
LoggingLevel
isn't captured by default as part of Traces' custom dimension because that data is already captured in the SeverityLevel
field. For information on how to reenable it, see the config options.Published by heyams over 2 years ago
Published by heyams over 2 years ago
Published by heyams over 2 years ago
Published by heyams over 2 years ago
Published by heyams over 2 years ago
Published by heyams over 2 years ago
Published by heyams over 2 years ago
Published by heyams over 2 years ago
Published by kryalama over 2 years ago
Published by heyams almost 3 years ago
Published by heyams almost 3 years ago
Updates applicationinsights-logging-log4j2
artifact to not pull in Log4j 2 dependency on its own. Users should already be bringing their own version of Log4j 2 (and should be upgrading that version or applying the mitigation steps from CVE-2021-44228). The update ensures that users have to bring their own version of Log4j 2 (#2002).
Please see #2008 for any other questions about Log4j 2.
Published by kryalama almost 3 years ago