Hi I am trying to use burrow with amazon msk version 1.1.1 with traffic between clients and brokers as only TLS encrypted traffic is allowed.
I tried using the following properties:
[tls.tlsonly]
certfile="/opt/ssl/kafkakeystore/client.crt"
keyfile="/opt/ssl/kafkakeystore/client.key"
cafile="/opt/ssl/kafkakeystore/ca.crt"
noverify=false
But I am getting the error level":"error","ts":1581337063.4007235,"msg":"failed to start client","type":"module","coordinator":"cluster","class":"kafka","name":"pre-glp1-glp2-int-msk3","error":"kafka: client has run out of available brokers to talk to (Is your cluster reachable?)"}
Burrow 1.3.2
and generalmills/burrowui
running and I'm wondering about the one consumer that seems unlike all the others ... its lag is very high and its topic is __consumer_offsets
-- Is my setup missing something? Or is it normal that the total lag
for this consumer keeps increasing and it has an ERR
state?
[consumer.myconsumers]
class-name="kafka"
cluster="mycluster"
servers=["host1:6667","host2:6667","host3:6667"]
hi there, I'm experiencing issues with burrow on windows 10.
I cloned a repository and run commandsdocker-compose build
anddocker-compose up
and
burrow dashboard failed to start, I checked logs and see
Reading configuration from /etc/burrow
Failed reading configuration: Config File "burrow" Not Found in "[/etc/burrow]"
docker-config
folder
"zk: not authenticated"
. I havent even tried Kerberos authentication with keytab because I can see in docs that its not really supported.Hi All,
Im working on to setup burrowv3 to monitor 2 kafka cluster consumers in a same configuration,
and added 2 kafka clusters end point in the same configuration by dividing it based on cluster name
But it works for only one cluster not for other cluster where i can see output of prod cluster but not of stg
Myquestion is - Can we use 2 kafka cluster endpoints in the same configuration to monitor?
If yes, Can someone help me to make necessary changes.
/metrics
endpoint, but am confused about how to use it.
intervals=10
configuration and a group which has committed 6 offsets for a partition, the completeness for that (group, partition) pair would be 0.6. As the window only moves forwards upon seeing a committed offset, this should mean that completeness should never decrease unless expire-group
seconds passes (default 7 days). Does this sound accurate?
@LamedB_twitter
I used the latest version with docker, and when I calling the /metrics I can't see the burrow_kafka_consumer_partition_lag metics. I can see all the burrow_kafka_topic_partition_offset but I want the lag, what might be wrong?
Was there a solution to this issue? I'm having the same problem: I've successfully build and deployed Burrow v1.3.4 in a k8s cluster, it seemingly can talk to Kafka & Zookeeper successfully, but the only Prometheus metrics it exports are burrow_kafka_topic_partition_offset
when really what I want is burrow_kafka_consumer_lag_total
. I feel I must have done something wrong, though in a test environment with broadly the same setup I had success, so I'm confused about what I could've done wrong :sweat_smile:
Hi guys,
Have a question whether you have an issue with group-denylist. I created a regex and config looks like this:
group-denylist="ˆ(?!crmgroup-222|issgroup-333).*$)"
Issue I'm meeting with is that I'm getting error mail if some other group which is not covered in regex like "test-group" is having an issue. I don't want to get an error email group for that one and that's the reason why I created this regex. No, anyone has similar experience or I'm doing something wrong?
client-profile
section of the config — https://github.com/linkedin/Burrow/wiki/Configuration#client-profile.
[client-profile.MYCLIENT]
kafka-version="2.x.x"
client-id="burrow-myclient"
sasl="PLAIN"
[sasl.PLAIN]
username="Adminuser"
password="Adminpassword"
handshake-first=false
[consumer.CLUSTER]
class-name="kafka"
cluster="CLUSTER"
client-profile="MYCLIENT"
That should be all you need.
[client-profile.test]
client-id="burrow-test"
kafka-version="0.11.0.2"
sasl="PLAINSS"
tls="mytlsprofile"
[sasl.PLAINSS]
handshake-first=true
username="superuser"
password="superuserpassword"
[tls.mytlsprofile]
certfile="path/to/certfile/file/wildcard.jks"
keyfile="path/to/keyfile/file/wildcard.jks"
noverify=true
Hi, facing issue with prometheus metrics. We are just getting burrow_kafka_topic_partition_offset and no other metrics, where as ideally we should have got all of these "burrow_kafka_consumer_partition_lag", "burrow_kafka_consumer_current_offset", "burrow_kafka_consumer_status".
Any configurations that needs to be updated to get all the metrics.
We are using kafka version 0.11.0.3. and its a secured kafka cluster.