store, query, frontend: add log.format flag #173
Merged
Conversation
This file contains 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
|
Looks like I need to fix some tests, add a DCO, and add a changelog now that the PR ID is known. Update: done. |
Default to "logfmt", the same as the upstream default. Also fix bug in which logLevel was not passed to query frontend. Signed-off-by: Craig Furman <craig.furman89@gmail.com>
craigfurman
force-pushed
the
log-format
branch
from
04ad8c6 to
82e824b
Compare
|
FYI, this is so we can change to json logs. |
|
Ping @metalmatze 😄 |
|
Makes a lot of sense! Thanks! |
2 tasks
|
Thanks @metalmatze! We are currently only using those components, but will be using them all soon. I've opened #178 adding it everywhere else. |
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.
Changes
store, query, frontend: add log.format flag
Default to "logfmt", the same as the upstream default.
Also fix bug in which logLevel was not passed to query frontend.
Verification
I've tested this in a dev environment (k3d).