Jorge Esteban Quilcate Otoya

Thanks for the workaround @timtebeek ! > Maybe a new tag would already be enough to fix the issue? > Although ideally swap Java 8 for 11, also given the...

@seglo thanks for the heads up! Unfortunately, it's not fixing the issue: ``` 2021-11-22 12:02:04,671 ERROR c.l.k.ConsumerGroupCollector$ akka://kafka-lag-exporter/user/consumer-group-collector-dev-cluster - Supervisor RestartSupervisor saw failure [3]: Failed to construct kafka consumer org.apache.kafka.common.KafkaException:...

Haven't tested it, but seems like #297 already solves this?

Thanks @seglo for tracking this! Wondering if targetting jdk17, as next LTS, would be a better alternative in the long term. Though not sure about the impact around scala deps,...

@vdesabou it works for me: https://gray-bee-8m5ifxwq.ws-us17.gitpod.io/ 

+1

@shakuzen the main difference between messaging to RPC is that we don't have the server (broker) span to name it. To get there, we would need to instrument the broker...

@adriancole yes, topic names will be available via tag I think. If it's not part of the instrumentation, finishedspanhandler could work, or setting remoteservicename manually as well. > So I'm...

@adriancole I remember we discussed something similar around jms instrumentation. Do you mean to have a `brave.messaging` layer to reuse on jms/kafka/..., right? I like the challenge, I will play...

@jorgheymans wouldn't be possible in the scenario you mentioned that consumer for the feeds from outside application is configured with a different MessagingTracing instance? Would this solve your use-case?