Adjust the charm logging to include the logger name#550
Draft
Adjust the charm logging to include the logger name#550
Conversation
mateoflorido
approved these changes
Jul 2, 2025
Member
mateoflorido
left a comment
There was a problem hiding this comment.
Great stuff! Thanks @addyess
Contributor
Author
|
Converted to draft waiting on feedback from ops |
Contributor
Author
Nevermind -- the ops issue canonical/operator#1880 is still open -- but it didn't seem they wanted to PR |
72c382d to
ef1a3b9
Compare
7f4168b to
afdad26
Compare
Contributor
Test results for commit afdad26Test coverage for afdad26 Static code analysis report |
Contributor
Test results for commit afdad26Test coverage for afdad26 Static code analysis report |
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
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.
Overview
Details
ops.logbut it uses the default FormatterDIff of a few logs: