[
https://issues.apache.org/jira/browse/KAFKA-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747079#comment-17747079
]
Bryan commented on KAFKA-15191:
-------------------------------
Strong interest from my perspective for end-to-end visibility of a flow,
including the Kafka portion
> Add support for Micrometer Observation
> --------------------------------------
>
> Key: KAFKA-15191
> URL: https://issues.apache.org/jira/browse/KAFKA-15191
> Project: Kafka
> Issue Type: New Feature
> Reporter: Marcin Grzejszczak
> Priority: Major
>
> I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together
> with Tommy Ludwig and Jonatan Ivanov).
> The idea of [Micrometer Observation|https://micrometer.io/docs/observation]
> is that you instrument code once but you get multiple benefits out of it -
> e.g. you can get tracing, metrics, logging or whatever you see fit.
> I was curious if there's interest in adding Micrometer Observation support so
> that automatically metrics, spans could be created and tracing context
> propagation could happen too. In other words metrics and tracing of this
> project could be created + if there are Micrometer Observation compatible
> projects, then they will join the whole graph (e.g. Spring Framework 6,
> Apache Dubbo, Resilience4j, Apache Camel etc.).
> If there's interest in adding that feature, I can provide a PR.
> Regardless of whether there's interest in adding this directly to Kafka I
> would like to discuss what would be the best way to add instrumentation to
> Kafka. Adding instrumentation means before the message is sent to Kafka I
> would like to access its headers and be able mutate them, and before the
> message is received from Kafka I would like to access the headers and
> retrieve its key-values to create e.g. a span.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
