How to reduce log level to warning from info

[Mahesh-Gunda-Maersk]

How to reduce log level to warning from info

[martin-helmich]

The replicator supports a --log-level flag, which you should be able to use.

kubernetes-replicator/main.go

Line 30 in 902b3c3

flag.StringVar(&f.LogLevel, "log-level", "info", "Log level (trace, debug, info, warn, error)")

The Helm chart has an args value which can be used to pass custom command-line arguments to the Deployment. Something like the following in your Helm values should do the trick:

args:
  - --log-level=warn

[Mahesh-Gunda-Maersk]

ok. was looking for something like this. will test this. Thank you.

[Mahesh-Gunda-Maersk]

Though I set log-level as warn, the log level is showing as an error .. is this expected? also when I set it to trace I see both debug, info & error logs. Please help us in understanding this behaviour

[Mahesh-Gunda-Maersk]

Hi, pls check if this behavior is fine. Thank you.

[martin-helmich]

Though I set log-level as warn, the log level is showing as an error .. is this expected? also when I set it to trace I see both debug, info & error logs. Please help us in understanding this behaviour

I'm unsure if I understand the issue. Setting a log level customarily results in logging items with a severity equal to OR HIGHER than the configured log level, so a log level of warn will also log anything more severe than warnings (like errors and panics).

[Mahesh-Gunda-Maersk]

yes, we are on the same page. I have set log-level to the warning, but I see logging severity as error. just want to understand if this behavior is expected. anything we need to worry about?

[martin-helmich]

Alright, then. 🙂 Regarding the actual logs with error severity: No, in normal operation, the replicator should not log any errors. What is the actual error that is being reported? I'm referring to the error field that is cropped in your screenshot.

[Mahesh-Gunda-Maersk]

below is the log snippet with log-level=warn

time="2023-04-19T06:13:15Z" level=error msg="could not replicate object to other namespaces" error="Replicated xyz-streams/local-abc-configuration to 7 out of 17 namespaces: 10 errors occurred:\n\t* Failed to replicate Secret xyzl-streams/local-abc-configuration -> kube-public: Failed to update secret kube-public/local-abc-configuration: secrets \"local-kafka-configuration\" already exists: Failed to update secret kube-public/local-abc-configuration: secrets \"local-kafka-configuration\" already exists\n\t ...........................

same error message for other secrets.

[Mahesh-Gunda-Maersk]

Hello @martin-helmich, were you able to reproduce this issue at your end? hope the error snippet shared helped.

[Mahesh-Gunda-Maersk]

sorry to bother you @martin-helmich. did you get a chance to look at the log snippet and do you have anything to comment or advise on this behavior?