Spring cloud gateway distribute to other service, transaction.id is different

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:

TIP 1: select at least one tag that further categorizes your topic. For example server for APM Server related questions, java for questions regarding the Elastic APM Java agent, or ui for questions about the APM App within Kibana.

TIP 2: Check out the troubleshooting guide first. Not only will it help you to resolve common problems faster but it also explains in more detail which information we need before we can properly help you.

Kibana version:7.10.2

Elasticsearch version:7.10.2

APM Server version:7.10.2

APM Agent language and version: 1.25.0 java

Browser version:

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:
1.create a spring cloud gateway application
2.create a service
3.visit a route, gateway distribute to A service, the gateway transaction.id is different from A service transaction.id

Errors in browser console (if relevant):

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

We probably don't support either an asynchronous mechanism used within the framework, or the web client it uses to make the routed request (maybe WebFlux client?)

probably?it is a pity that apm can't support the framework. The framework is based on WebFlux .Can we fit it ?

Yes, that's the word I use when I have an hypothesis that is not verified. You are welcome to verify and let us know, or wait until we get to that.

Our agent's support for WebFlux is still experimental, partly because we did not get to the HTTP client implementation yet. You are welcome to register to receive notifications from the related GitHub issue.

Yes. If you don't want to wait for the inherent support, check out our public API. It now offers new APIs to create exit spans and set their destination service metadata so that the downstream service is treated as such and added to the service map.

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