Open zachgilbert-upwork opened 3 months ago
Interesting catch! are you willing to open a PR with the change?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
Report
With the addition of the automaxprocs package to set GOMAXPROCS (https://github.com/kedacore/keda/issues/4999), the KEDA operator now prints one console type log on startup, then switches to the format configured by
logging.operator.format
:We are running KEDA in an environment where this is breaking our log ingestion, as we expect only one log format. The way to disable this logging, or implement it with the same logger as the rest app, is documented here: https://github.com/uber-go/automaxprocs/issues/18.
Expected Behavior
When setting the
logging.operator.format
tojson
, I expect all logs produced by the KEDA operator to be in JSON format.Actual Behavior
When running KEDA operator, there is one log printed by the
automaxprocs
package that doesn't respect the format as configured by the user.Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.13.1
Kubernetes Version
1.29
Platform
Amazon Web Services
Scaler Details
No response
Anything else?
No response