azure-deprecation / dashboard

Notices about Azure services & features being deprecated
https://azure-deprecation-notices.cloud
MIT License
134 stars 6 forks source link

Azure Application Insights SDK for Java v2.X is retiring on September 30th, 2025 #265

Open azure-deprecation-automation opened 2 years ago

azure-deprecation-automation commented 2 years ago

Azure Application Insights SDK for Java v2.X is retiring on September 30th, 2025

Deprecation ID: d7be673b-1ec2-4927-a3ab-454a59cc44a0 Deadline: Sep 30, 2025 Impacted Services:

More information:

Notice

Here's the official report from Microsoft:

On 30 September 2025, we’ll be retiring the application insights Java 2.X SDK; after that date it’ll no longer be supported. Before that date, we recommend you upgrade to OpenTelemetry-based Java 3.X auto-instrumentation, which provides all the functionality of the application insights Java 2.X SDK plus new ones, including:

  • Expanded distributed tracing auto-collection including the most common Azure SDKs, MongoDB, Kafka, Cassandra (and more)
  • JMX and micrometer metrics auto-collection
  • Codeless onboarding for easier deployments and upgrades

If you choose to not upgrade, your data will continue to flow to application insights. However, we’ll be unable to support any Azure support cases opened on this SDK, and you won’t receive the latest product features.

Timeline

Phase Date Description
Announcement Sep 30, 2022 Deprecation was announced
Deprecation Sep 30, 2025 SDK will no longer be supported.

Impact

Azure Application Insights SDK for Java v2.X is retiring on September 30th, 2025 and migration to Java SDK v3.X auto-instrument is required.

Required Action

A migration guide is provided here.

Here's the official report from Microsoft:

To avoid being on an unsupported SDK, upgrade to application insights Java 3.X auto-instrumentation by 30 September 2025.

Contact

You can get in touch through the following options:

azure-deprecation-automation commented 2 years ago

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.