This repository has been archived by the owner on Oct 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 29
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 <[email protected]>
k-wall
added a commit
to k-wall/strimzi-canary
that referenced
this issue
Feb 4, 2022
Signed-off-by: kwall <[email protected]>
k-wall
added a commit
to k-wall/strimzi-canary
that referenced
this issue
Feb 4, 2022
Signed-off-by: kwall <[email protected]>
k-wall
added a commit
to k-wall/strimzi-canary
that referenced
this issue
Feb 6, 2022
Signed-off-by: kwall <[email protected]>
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 <[email protected]>
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 <[email protected]> * Avoid mutation of sarama.Logger by go routines without mutex (Logger.SetOutput protects by mutex so is safe) Signed-off-by: kwall <[email protected]> * organise for goroutine within watcher to complete Signed-off-by: kwall <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: