Kafka / Spring Boot 3.4 & Java APM Agent

Elastic Observability APM
4

I think it could be worth trying the new EDOT Java agent instead to see what is being captured on jvm/pod-3.

Are all the 3 operations executed synchronously when processing a message ?

There are a few differences where it could help:

  • the need for trace_methods should be removed as all the spans are being captured with and without a transaction (unlike the Elastic APM Java agent which requires a transaction).
  • it should have a more exhaustive coverage for instrumentation, which probably includes your use-cases with Kafka

When testing I would suggest to check those things in order:

  1. do you get a span/transaction for every message received by your custom consumer ?
  2. are the calls to mongodb and grpc properly captured ?
  3. are the calls to kafka to publish properly captured ?
1 Like