Database update logs are logged to stderr

[bfil]

The dashboard-metrics-scraper pod writes the following logs to stderr every minute:

{ "level": "info", "msg": "Database updated: 1 nodes, 20 pods" }

It would be better to log these to stdout since they are info level logs.

I've also noticed a red herring in the server code when setting up the logger, where the comment says "Output to stdout instead of the default stderr", but the code does the opposite:

log.SetOutput(os.Stderr)

[AndrewDryga]

There are people that believe that progress logs should be also written to stderr and if that's how maintainers decide to keep it - we need a way to filter out INFO level logs entirely, otherwise, our stackdriver logs are filled with errors. For Stackdriver everything in stderr is an error unless your JSON has severity property set to info and there is no way to change that.

Maybe we can add a JSON log format option which would use severity field instead of level?

[AndrewDryga]

A similar issue exists in external-dns: kubernetes-sigs/external-dns#1616

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[pierluigilenoci]

@bfil I did this #45
Somehow it solves the question.

For the log level you can just use the --log-level=warn option.