Kafka Bridge metrics
#1034
Replies: 3 comments 5 replies
-
|
So I just ran Strimzi 0.47.0 and using the bridge 0.32.0. strimzi_bridge_kafka_producer_record_send_total
strimzi_bridge_kafka_producer_request_latency_avgI can see them in the output. Just using curl on the curl -s http://localhost:8080/metrics | grep strimzi_bridge_kafka_producer_record_send_total
# HELP strimzi_bridge_kafka_producer_record_send_total The total number of records sent. kafka.producer:name=null,type=producer-metrics,attribute=record-send-total
# TYPE strimzi_bridge_kafka_producer_record_send_total counter
strimzi_bridge_kafka_producer_record_send_total{clientId="producer-1",topic="my-topic",type="producer-topic-metrics"} 5.0
strimzi_bridge_kafka_producer_record_send_total{clientId="producer-1",type="producer-metrics"} 5.0curl -s http://localhost:8080/metrics | grep strimzi_bridge_kafka_producer_request_latency_avg
# HELP strimzi_bridge_kafka_producer_request_latency_avg The average request latency in ms kafka.producer:name=null,type=producer-metrics,attribute=request-latency-avg
# TYPE strimzi_bridge_kafka_producer_request_latency_avg gauge
strimzi_bridge_kafka_producer_request_latency_avg{clientId="producer-1",type="producer-metrics"} 24.8
strimzi_bridge_kafka_producer_request_latency_avg{clientId="producer-1, node-id=node--1",type="producer-node-metrics"} NaN
strimzi_bridge_kafka_producer_request_latency_avg{clientId="producer-1, node-id=node-0",type="producer-node-metrics"} NaN
strimzi_bridge_kafka_producer_request_latency_avg{clientId="producer-1, node-id=node-2",type="producer-node-metrics"} 24.8Regarding the # HELP strimzi_bridge_http_server_requests_total Number of processed requests
# TYPE strimzi_bridge_http_server_requests_total counter
strimzi_bridge_http_server_requests_total{code="204",method="GET",path="/ready",} 26.0
strimzi_bridge_http_server_requests_total{code="204",method="GET",path="/healthy",} 26.0
strimzi_bridge_http_server_requests_total{code="200",method="POST",path="/topics/my-topic",} 5.0Of course it means it should be addressed in the Prometheus rules. |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
I opened this PR to fix this in the future Strimzi release strimzi/strimzi-kafka-operator#12057 |
Beta Was this translation helpful? Give feedback.
-
|
Hi, When I created a consumer through the bridge, I started receiving |
Beta Was this translation helpful? Give feedback.
-
|
You just need sending messages. This is what I did. Just simple HTTP calls to send messages, and the producer related metrics showed up. |
Beta Was this translation helpful? Give feedback.
-
|
Are you running the bridge locally? I ran a 0.32 bridge locally, connecting to the same Kafka cluster, and then the producer metrics appeared. But with the bridge on Kubernetes, these metrics are not being generated for me. Below is the log from the bridge on Kubernetes. It seems that after producing the message, it is closing the producer and removing the related metrics. Config Log |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
It's working for me on Kubernetes but without SSL. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I can successfully consume the messages produced. And the consumer metrics are being generated, but the producer ones are not. I ran a test using plain on 9092 with SCRAM and the same problem occurs, so it's not TLS. It seems to me that the issue is that in Kubernetes it is closing the producer right after completing the message recording, which is why it removes the metrics. Locally, it does not close the producer. Is there a difference in the bridge's behavior between these two environments (standalone and Kubernetes)? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
There is no difference. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have Kafka Bridge 0.32 installed on Kubernetes together with Strimzi 0.47. The Bridge has
enableMetrics: trueand it is exposing them at /metrics.However, when configuring Prometheus and Grafana using the examples provided in the package, some of the Bridge alerts and dashboard panel seem to reference metrics that are not being exposed by the Bridge.
For example:
Are the examples/metrics outdated?
Beta Was this translation helpful? Give feedback.
All reactions