Jacob Bresciani

I've been playing with that file locally, I can confirm that's part of it. There is also an issue with line 91 in the same file. https://github.com/linkedin/Burrow/pull/628/files#diff-0f9ca663563a0c68cf314325f84c48b8R91 If you remove...

``` diff --git a/core/internal/httpserver/prometheus.go b/core/internal/httpserver/prometheus.go index 92456f5..2a9248f 100644 --- a/core/internal/httpserver/prometheus.go +++ b/core/internal/httpserver/prometheus.go @@ -63,33 +63,29 @@ func (hc *Coordinator) handlePrometheusMetrics() http.HandlerFunc { consumerStatus := getFullConsumerStatus(hc.App, cluster, consumer) if consumerStatus ==...

with the merger of 638 and 700 I believe this is now fixed and can be closed.

I am a Go noob but I was able to get SCRAM sha256 and sha512 working using this patch ``` diff --git a/core/internal/helpers/sarama.go b/core/internal/helpers/sarama.go index 99458a1..3bdf0d7 100644 --- a/core/internal/helpers/sarama.go +++...

my config currently looks like ``` [zookeeper] servers=['10.0.0.11:2182', '10.0.0.12:2182', '10.0.0.13:2182'] timeout=6 root-path="/burrow/notifier" [client-profile.mycluster] client-id="burrow" servers=['10.0.0.1:9092', '10.0.0.2:9092', '10.0.0.3:9092', '10.0.0.4:9092', '10.0.0.5:9092'] sasl="mycluster" [sasl.mycluster] handshake-first=true algorithm=sha512 [cluster.mycluster] class-name="kafka" client-profile="mycluster" offset-refresh=10 servers=['10.0.0.1:9092', '10.0.0.2:9092', '10.0.0.3:9092',...

I've since moved to SASL_SSL and my config now looks like ``` [zookeeper] servers=['10.0.0.11:2182', '10.0.0.12:2182', '10.0.0.13:2182'] timeout=6 root-path="/burrow/notifier" [client-profile.mycluster] client-id="burrow" kafka-version="2.2.0" sasl="mycluster" tls="mycluster" [sasl.mycluster] handshake-first=true [tls.mycluster] cafile="/certs/kafka_ca_cert.pem" noverify=true [cluster.mycluster] class-name="kafka"...

I'm seeing the same issue that @tonsV2 and @SkylerLutz are describing, I'm on v1.39.1 installed from brew on OSx 11.6.8. The first deploy shows logs properly, if the dev cycle...

https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/plugins/node/opentelemetry-instrumentation-winston/package.json#L51 it's listed as a devDependencies and not a dependancy, which explains it and confirms your theory @c0j0s