You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fil Karnicki (Jira)" <ji...@apache.org> on 2022/03/28 18:20:00 UTC

[jira] [Comment Edited] (FLINK-26617) Pass Kafka headers to remote functions and egresses

    [ https://issues.apache.org/jira/browse/FLINK-26617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513549#comment-17513549 ] 

Fil Karnicki edited comment on FLINK-26617 at 3/28/22, 6:19 PM:
----------------------------------------------------------------

Hi [~trohrmann]. In my current project, inside remote functions, we create a fair amount of child spans (and children of those, and so on) in order to get very granular tracing and logging, all of which lands in Jaeger. What we can't currently can't do is connect it all to the spans triggered by initial user actions, and whatever further processing happens on the back of our egress messages. Our support teams rely on being able to search by tags in jaeger in order to find the entire trace, and get the full 'story'. We can only add these tags in our remote functions, so we really do need the SDK to be aware of spans, if possible


was (Author: JIRAUSER284249):
Hi [~trohrmann]. In my current project, inside remote functions, we create a fair amount of child spans (and children of those, and so on) in order to get very granular tracing and logging, all of which lands in Jaeger. What we can't currently can't do is connect it all to the spans triggered by initial user actions, and whatever further processing happens on the back of our egress messages. Our support teams rely on being able to search by tags in jaeger in order to find the entire trace, and get the full 'story'. We can only add these tags in our remote functions, so we really do need the SDK to either be aware of spans, if possible

> 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)