Conversation
….DurableTask Signed-off-by: tomflenner <flennertom@gmail.com>
Signed-off-by: tomflenner <flennertom@gmail.com>
Collaborator
|
Thank you very much for your contribution @tomflenner ! I appreciate it! |
Author
|
Always a pleasure @WhitWaldo ! 🤝🏻 |
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
2 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.
Description
This pull request updates the logging category/module name used in .NET logging from
Microsoft.DurableTasktoDapr.DurableTask. This change reflects the transition to a Dapr-maintained fork of the original Microsoft Durable Task library.Motivation
Dapr has forked Microsoft.DurableTask to introduce customizations and enhancements specific to the Dapr ecosystem. To ensure accurate logging, observability, and filtering, it's important that log entries are correctly attributed to the new module name
Dapr.DurableTaskrather than the original one.Impact
This change is purely internal and affects only the logging metadata. There is no functional impact on runtime behavior, but log management tools and filters relying on the old category name may need to be updated.