-
Notifications
You must be signed in to change notification settings - Fork 19
Add/increase execution logging #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR enhances logging visibility by adding orchestration names to log messages and promoting key activity/entity execution logs from debug to info level.
- Extracts and includes orchestration names in orchestration-related log messages
- Promotes activity and entity execution log messages from debug to info level for better visibility
- Adds a new log message at the beginning of orchestration replay
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
| orchestration_name = "<unknown>" | ||
| orchestration_started_events = [e for e in old_events if e.HasField("executionStarted")] | ||
| if len(orchestration_started_events) >= 1: | ||
| orchestration_name = orchestration_started_events[0].executionStarted.name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is QoL, not sure if it is worth the time to include, given it involves another iteration over old_events.
In durabletask-dotnet, they use this logic
https://github.com/Azure/durabletask/blob/8576bc5777119c673857b87c1e85992a1111d437/src/DurableTask.Core/OrchestrationRuntimeState.cs#L148
Resolves #47