-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to change canary logging verbosity and enable/disable Sarama logger at runtime #166
Milestone
Comments
k-wall
added a commit
to k-wall/strimzi-canary
that referenced
this issue
Feb 3, 2022
k-wall
added a commit
to k-wall/strimzi-canary
that referenced
this issue
Feb 3, 2022
Signed-off-by: kwall <kwall@apache.org>
k-wall
added a commit
to k-wall/strimzi-canary
that referenced
this issue
Feb 4, 2022
Signed-off-by: kwall <kwall@apache.org>
k-wall
added a commit
to k-wall/strimzi-canary
that referenced
this issue
Feb 4, 2022
Signed-off-by: kwall <kwall@apache.org>
k-wall
added a commit
to k-wall/strimzi-canary
that referenced
this issue
Feb 6, 2022
Signed-off-by: kwall <kwall@apache.org>
k-wall
added a commit
to k-wall/strimzi-canary
that referenced
this issue
Feb 9, 2022
(reported by go test --race ./...) Signed-off-by: kwall <kwall@apache.org>
scholzj
pushed a commit
that referenced
this issue
Feb 9, 2022
* Fix data race issue introduced by #166 (reported by go test --race ./...) Signed-off-by: kwall <kwall@apache.org> * Avoid mutation of sarama.Logger by go routines without mutex (Logger.SetOutput protects by mutex so is safe) Signed-off-by: kwall <kwall@apache.org> * organise for goroutine within watcher to complete Signed-off-by: kwall <kwall@apache.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently it's possible to specify the logging verbosity of the canary itself and enabling/disabling the Sarama logger via environment variables.
When an error occurs in a canary instance running, it would be great to increase/enable both at runtime without restarting the canary (because the issue could disappear).
One way could be having an "optional" configuration file for the canary (specifying its path via an env var?) where configuration parameters could be specified and overriding what's defined via env vars.
The canary could then have a periodic internal service watching changes to this file and change internal config accordingly.
The text was updated successfully, but these errors were encountered: