apache / apache/camel-quarkus

Micromether Metrics with prometheus not showing Kafka metrics from camel-quarkus-kafka

Open
#4,313 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
302
Forks
232
Avg merge
1d 20h
Merged PRs (30d)
114

Description

In my camel-quarkus-kafka project, producer Kafka metrics are not showing up in the [Micrometer prometheus endpoint](http://localhost:8080/q/metrics).

The [example project](https://github.com/mmacphail/example-camel-kafka) is available on github. If the project is ran, no Kafka metrics will appear in [Micrometer prometheus endpoint](http://localhost:8080/q/metrics). Other metrics such as camel metrics appear.

My route:
```java
public class ExampleRoute extends RouteBuilder {

@Override
public void configure() throws Exception {
from(timer("foo").period(1000))
.to(kafka("test"));
}
}
```

Configuration:
```text
quarkus.camel.metrics.enable-message-history=true
quarkus.kafka.devservices.enabled=true
quarkus.micrometer.binder.kafka.enabled=true
```
I would expect the third property to do the trick according to the [Quarkus Micrometer documentation](https://quarkus.io/guides/micrometer#quarkus-micrometer_quarkus.micrometer.binder.kafka.enabled).

Dependencies:
```xml


io.quarkus
quarkus-resteasy-reactive-jackson


org.apache.camel.quarkus
camel-quarkus-core


io.quarkus
quarkus-micrometer-registry-prometheus


org.apache.camel.quarkus
camel-quarkus-kafka


io.quarkus
quarkus-resteasy-reactive


org.apache.camel.quarkus
camel-quarkus-micrometer


org.apache.camel.quarkus
camel-quarkus-timer


io.quarkus
quarkus-micrometer


io.quarkus
quarkus-arc


io.quarkus
quarkus-junit5
test


io.rest-assured
rest-assured
test


```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked example project and its Java route, then run it with the listed Quarkus Kafka, Micrometer, and Prometheus configuration. Inspect the /q/metrics endpoint and compare the missing Kafka metrics with the Camel metrics that appear. Done means the example exposes producer Kafka metrics at the Prometheus endpoint, with a regression test if the repository provides a suitable test location.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kafka, prometheus
Domain
observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.