Custom Distributed transactions linked with instrumented spans

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.2

Elasticsearch version: 7.2

APM Server version: 7.2

APM Agent language and version: node.js 3.2 and rum 4.6
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): I want to create custom transactions that the instrumented http transactions are linked to. Currently, the instrumented transactions are their own transactions.

Steps to reproduce:

Errors in browser console (if relevant):

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

I have a react application along with services in node.js and java. A button click in react will fire off several http requests to the node and java services in parallel. I would like to have a single transaction that ties it all together. One trace per click.

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