Does apm-java-agent support java.util.concurrent.Future

If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text :slight_smile:

Kibana version:7.4

Elasticsearch version:7.4

APM Server version:7.4

APM Agent language and version:1.16

Browser version:google

Original install method (e.g. download page, yum, deb, from source, etc.) and version:

Fresh install or upgraded from other version?

Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):

Steps to reproduce:

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Not sure what you mean by supporting Futures - is it the duration of get invocations? Then we do not.
If it is about context propagation when using concurrent frameworks, then we currently support ExecutorService and we will soon extend that to supporting additional frameworks.

thank you for your reply. i still
i use the java-util-concurrent-future to in the project,when i use java agent ,some traces can not show,so t ask the question.
i see, something can be shown,but not all things

Please try out this snapshot agent. If it doesn't make a difference, you may be using several async frameworks, some of which we support and some we do not.

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.