[
https://issues.apache.org/jira/browse/FLINK-26617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514596#comment-17514596
]
Till Rohrmann commented on FLINK-26617:
---------------------------------------
If this is a requirement, then I guess we need to send the span context to the
remote functions. I think this should be doable as this is not a lot of
information.
At the moment I am not 100% sure what things need to change in order to fully
support tracing in SF. To explore this and the requirements, I'd be fine if you
explored it using the example of Kafka records with spans attached. Based on
that we could think about how to generalize the mechanism so that it also works
with other ingresses/egresses.
> Pass Kafka headers to remote functions and egresses
> ---------------------------------------------------
>
> Key: FLINK-26617
> URL: https://issues.apache.org/jira/browse/FLINK-26617
> Project: Flink
> Issue Type: Improvement
> Components: Stateful Functions
> Reporter: Fil Karnicki
> Priority: Minor
>
> Typically OpenTelemetry (FLINK-22390) tracing spans get passed in kafka
> headers. We could be passing not only the Kafka ConsumerRecord value, but
> also the headers to remote functions, if the user configures their kafka
> ingress to do so
> Similarly, kafka egresses could be configurable so that headers get passed on
> via the KafkaProducerRecord proto to kafka
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
