[
https://issues.apache.org/jira/browse/FLINK-26617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513227#comment-17513227
]
Till Rohrmann commented on FLINK-26617:
---------------------------------------
Thanks for creating this ticket [~Fil Karnicki]. I think the topic of tracing
is very interesting as it opens SF up for better understanding what is going on.
Ideally, we can solve this problem generically as tracing is also interesting
for other ingresses and SF calls in general. I think what we would need to add
to the runtime is support for creating/deriving spans and propagating their
contexts.
I am not sure whether this information really needs to be forwarded to a remote
function unless the remote function can spawn external calls that need the
context as well. That way we don't need SDK specific handling logic. However,
we would need to adjust the ingresses and egresses to understand the
span/context field of a message.
> 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)
