Skip to content

No logging of WiredTiger progress messages - #14968

Merged
fniessink merged 1 commit into
masterfrom
mongo-logging
Nov 5, 2026
Merged

fniessink merged 1 commit into
masterfrom
mongo-logging

Conversation

@fniessink

Copy link
Copy Markdown
Member

The database no longer logs the progress messages of the WiredTiger storage engine. The database image now passes the --quiet flag to MongoDB itself, so the database also logs less when deployed with the Helm chart. If you copied command: --quiet from the Quality-time compose file into your own compose file, you may want to remove it, as it overrides the new default. See the deployment documentation.

Closes #14959.

The database no longer logs the progress messages of the WiredTiger storage engine. The database image now passes the `--quiet` flag to MongoDB itself, so the database also logs less when deployed with the Helm chart. If you copied `command: --quiet` from the *Quality-time* compose file into your own compose file, you may want to remove it, as it overrides the new default. See the [deployment documentation](deployment.md#configuring-logging-optional).

Closes #14959.
@sonarqubecloud

sonarqubecloud Bot commented Nov 5, 2026

Copy link
Copy Markdown

@fniessink
fniessink merged commit 4a82459 into master Nov 5, 2026
35 checks passed
@fniessink
fniessink deleted the mongo-logging branch November 5, 2026 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Plain log output when stdout is not a terminal

1 participant