log line inconsistency

[frzifus]

Describe the bug
Seems we use plain logrus in some places instead of the propagated logr.Logger wrapper. on one hand this leads to bad readability, on the other hand i had problems to change the log level in all places at once.

To Reproduce
Steps to reproduce the behavior:

1. Deploy Operator
2. Deploy Jaeger
3. View Operator logs

Expected behavior

• Seeing the same format of logs in every line.
• Being able to change log-levels globally.

Screenshots

Version (please complete the following information):

• Jaeger version: 1.32.0

[iblancasa]

What do you think about adding something to ensure the logging is not done using logrus directly (from the CI, for instance)? Is something I can work on.

[frzifus]

sure, what did you have in mind? Some kind of linting rule? I wouldn't prioritize it too highly, but it would certainly be helpful.

[iblancasa]

Yes. Something like looking for usages of logrus.<Logging function> and fail when something is found.
I know we first need to fix this but is to avoid new issues in the future. What do you think?

[frzifus]

I'm not sure if this will adequately address the issue. Imports are often renamed. Found this in cmd/generate.

e.g.

	log "github.com/sirupsen/logrus"

[iblancasa]

Where is the logr.Logger wrapper located? I'm not able to find it @frzifus