fix(qe): filter-in debug traces for mongo db queries regardless of global logger level #3310
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.
Fixes prisma/prisma#15084
#2752 added mongo logging, and as part of that it changed the logging configuration for the node API to ensure that regardless of their level, mongo queries were always logged:
prisma-engines/query-engine/query-engine-node-api/src/logger.rs
Lines 39 to 48 in abd71fc
However, the same change wasn't added to the query-engine server logging configuration. And because mongo logs queries using the tracing's debug macro. Those traces weren't emitted to standard output, and eventually processed by the Prisma client.
This patch fixes the situation by configuring the logger for the query-engine server to select queries logged in debug mode.