Removes appinsights module from java-logging #639
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull request overview
This PR removes the deprecated java-logging-appinsights module from the java-logging library as part of upgrading to version 7.0.0. The AppInsights 2.x SDK is no longer supported, and teams have already migrated to using Microsoft's agent directly via Dockerfile configurations rather than this module.
Key Changes:
- Completely removes the
java-logging-appinsightsmodule and all its associated code - Updates the main README with migration instructions for teams upgrading from 6.x
- Removes the module reference from
settings.gradle
Reviewed changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| settings.gradle | Removes the java-logging-appinsights module from the multi-module project configuration |
| java-logging-appinsights/build.gradle | Deletes the entire build configuration for the appinsights module |
| java-logging-appinsights/README.md | Removes comprehensive documentation about AppInsights SDK 2.x usage |
| java-logging-appinsights/src/main/resources/logback-appinsights.xml | Removes logback appender configuration for AppInsights |
| java-logging-appinsights/src/main/resources/META-INF/spring.factories | Removes Spring Boot auto-configuration registration |
| java-logging-appinsights/src/main/java/.../AppInsightsAutoConfiguration.java | Deletes Spring auto-configuration class that registered AppInsights beans |
| java-logging-appinsights/src/main/java/.../ContextVersionInitializer.java | Removes custom telemetry context initializer |
| java-logging-appinsights/src/main/java/.../SyntheticHeaders.java | Deletes utility class for synthetic test headers |
| java-logging-appinsights/src/test/resources/application.yml | Removes test configuration file |
| README.md | Updates main documentation with migration guidance and removal notice |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
linusnorton
approved these changes
Dec 18, 2025
jordankainos
approved these changes
Dec 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://tools.hmcts.net/jira/browse/DTSPO-24922
AppInsights 2.x is no longer in support
We had it defaulted to this version in java-logging.
Teams got around this in a few ways:
App Insights agent is added into base images for java
We have no use of 2.x SDK anymore even though it's defined in this module as a hard dependency, meaning Dockerfile override or non-use.
Suggestion is that we publish a new
7.0.0version of java-logging which removes thelogging-appinsights- so when teams upgrade they can remove the dependency line i.e. removingThis change coupled with major version upgrade should remove confusion about 2.x SDK and remove any risk that we're still using it anywhere