What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

The logging level for the MongoDB Kubernetes Operator deployment environment is controlled by the operator.env setting
in configuration YAML. This setting affects both the log verbosity level and log format:

If operator.env is set to dev:
Log Level: debug
Log Format: text

If operator.env is set to prod (default):
Log Level: info
Log Format: json

What would you like to see happen?

Describe the desired outcome or enhancement.

To increase log verbosity to debug during investigations, set env to dev. Otherwise, keep it as prod for standard informational logs.

We have the possibility only to increase log verbosity, but we want to decrease log verbosity.
What possibilities do we have to make this change, to decrease log verbosity, for example, to errors and warnings only?

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

We are storing the logs for 30 days on external storage and it gets filled up quite quickly.

Our goal is to reduce the logs to the minimum possible in terms of storage consumption.

What steps, if any, are you taking today to manage this problem?

Open a Case for support