feat: add "Consistent Logs Style" section to M-LOG-STRUCTURED #30
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
geeknoid
reviewed
Dec 4, 2025
| "Database migration failed. Rolling back changes. error: {{error.message}}, migration: {{db.migration.version}}" | ||
| ``` | ||
|
|
||
| > **Note:** Include all properties in the message template for easier debugging without inspecting structured data separately. |
Member
There was a problem hiding this comment.
This is antithetical to cost controls. Ultimately, we want all logs to be strictly name/value pairs without a full string needing to be formatted and sent over the wire.
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.
I see a lot of log message around, we can provide some recommendation to unify these