CBG-3286 Per-db console log settings #6348
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
bbrks
changed the title
bbrks
force-pushed
the
per-db-console-log-settings
branch
from
fb23d92
to
85a4f82
Compare
JRascagneres
previously approved these changes
Aug 10, 2023
adamcfraser
reviewed
Aug 11, 2023
IsaacLambat
requested changes
Aug 15, 2023
IsaacLambat
approved these changes
Aug 15, 2023
bbrks
changed the title
bbrks
added a commit
that referenced
this pull request
Sep 7, 2023
1 task
bbrks
added a commit
that referenced
this pull request
Sep 7, 2023
bbrks
added a commit
that referenced
this pull request
Mar 28, 2024
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.
CBG-0000
Stores a reference to the database log configuration inside the database-scoped log context, so that we're able to look it up when we log to determine whether to emit the console log or not.
This allows databases to define their own console log level and log keys. Neither of the two settings takes precedence. They're additive (either node OR db log level/key are checked when writing a log line, if either match, it will be logged).
Integration Tests
GSI=true,xattrs=truehttps://jenkins.sgwdev.com/job/SyncGateway-Integration/000/