Add session ID to client log context#1809
Merged
Merged
Conversation
Include the OPC UA session identifier in MDC once it becomes available so concurrent session activity can be correlated reliably.
kevinherron
marked this pull request as ready for review
July 15, 2026 13:38
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
instance-idandsession-idMDC setup in scoped helpersWhy
Concurrent client session activity can otherwise be difficult to correlate from logs using only the FSM instance identifier. The session identifier provides a direct link between lifecycle, keep-alive, transfer, initialization, reactivation, and close messages.
Validation
mise exec -- mvn -q spotless:applymise exec -- mvn -q clean compileNo unit tests were added or run for this change.