Dear Elastic APM fans…
I have a very tricky situation, we started using elastic APM; and we are in learning curve phase.
Most of the times, the dependencies do not turn up. But sometimes for some other service, it does show the dependencies.
But when I enter into ‘transactions’ link, I get the dependencies in trace. Yes, some of our dev colleagues did instrument there.
Attached: Images should give some information.
Kibana version: Kibana: 7.14.2
Elasticsearch version: 7.14.2
APM Server version:7.12.1
APM Agent language and version:
Elastic APM Java Agent / 1.30.1
Browser version: Chrome Version 101.0.4951.64 (Official Build) (x86_64)
Original install method (e.g. download page, yum, deb, from source, etc.) and version:
CRD
Fresh install or upgraded from other version?
Upgraded from previous version
Is there anything special in your setup?
Nothing special setup. For some services in the same cluster (developed for Java 11), things work as expected. But for most of the services, the dependencies do not turn up . Most of the dependencies are in gRPC calls to start with. These gRPC servers are implemented in Java. But when you drill down to transactions, one can see the dependencies.
Logs
I tried looking into traces, it did not help much.
Description of the problem including expected versus actual behavior.
It is expected to get the dependencies. Is there anything missing?
