Add attempt number to structured activity logger #1020
Merged
+3
−0
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
evansandoval
requested review from
Groxx,
abhishekj720,
natemort,
shijiesheng,
dkrotx,
taylanisikdemir and
demirkayaender
as code owners
natemort
approved these changes
Aug 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed?
Added attempt number logging to activity execution. This includes:
Why?
To improve observability and debugging capabilities for activity executions by including the Attempt number
How did you test it?
Tested locally against the java-samples and verified that attempt numbers showed up.
Will also rely on GitHub Actions builds
Potential risks
Very low risk change, only adds additional logging context, doesn't modify core business logic
Release notes
Minor enhancement: Activity execution logs now include attempt number for better retry debugging and observability.
Documentation Changes
No configuration or setup documentation changes required. This is an internal logging enhancement that improves observability without requiring user configuration changes.