Logging solely to stdout/stderr at the specified log level about mongodb-kubernetes-operator HOT 10 CLOSED

Hi! Finally found some time to create a PR:

#1489

The gist is that setting agent.logFile: /dev/stdout will unset the -logFile command line option which make the agent log to stdout.

Please review. Any comments welcome.

from mongodb-kubernetes-operator.

I am having the same issue after upgrading the mongodb-operator from 0.7.6 to 0.8.3 (Looks like anything >0.7.8 has this issue)
By default it's logging as per AGENT_LOG_LEVEL to AGENT_LOG_FILE=/var/log/mongodb-mms-automation/automation-agent.log
However the moment I change AGENT_LOG_FILE=/dev/stdout it started logging everything like .trace as well as .debug
This is causing too much logging

Moreover, Following error is being logged while using logFile=/dev/stdout

[.error] [src/main/cm.go:main:118] Failed to create AsyncRollingFileAppender for full log file : open /dev/stdout-verbose: permission denied
[.error] [src/main/cm.go:main:119] [02:01:44.428] Failed to setup logging! :  Failed to create AsyncRollingFileAppender for full log file : open /dev/stdout-verbose: permission denied

from mongodb-kubernetes-operator.

The problem here seems to be that the mongo agent requires the absence of the logFile cmdline option to log to /dev/stdout. So if in the operator config the logFile is absent or set to /dev/stdout the cmdline should not include the logFile option part.

See:
https://stackoverflow.com/questions/13506198/mongodb-log-mongod-to-stdout

Although the official docs do not mention this:
https://www.mongodb.com/docs/ops-manager/current/reference/mongodb-agent-settings/#logging-settings

from mongodb-kubernetes-operator.

The issue is still actual

from mongodb-kubernetes-operator.

Damn, just deployed an operator upgrade and got paged that our log volumes are filling up with bloat...

from mongodb-kubernetes-operator.

This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.

from mongodb-kubernetes-operator.

Issue is still valid and blocking the upgrade of mongodb-operator from 0.7.8 onwards

from mongodb-kubernetes-operator.

@schans change has been merged. Closing this Issue

Please follow this setting: #1439 (comment) to send to stderr/stdout instead of a file

from mongodb-kubernetes-operator.

Perfect. Thanks for your help!

from mongodb-kubernetes-operator.

Thank you! This is a huge help 🙏

from mongodb-kubernetes-operator.