Service Map cannot connect the services (both services uses the same agent)

[alidrsn]

No description provided.

[michaelhyatt]

Hi @alidrsn Are you referring to the Service Map connection, or seeing 2 Mule flows as the same trace in the APM trace view?

[alidrsn]

Hi @alidrsn Are you referring to the Service Map connection, or seeing 2 Mule flows as the same trace in the APM trace view?

Hi @michaelhyatt, yes I mean two services are not linking/drawing each other on Kibana/Service Map

According to elastic documentation, traceparent header would be missing. Is there any other configuration required from Mulesoft side ?

[michaelhyatt]

Can you please retrieve the JSON documents representing the transactions and spans, so I can have a look at it?

[alidrsn]

It is too hard to send all raw data (also not allowed). However,

What I can show you below; these are two applications sharing the same traceID, App1 is calling App2 in the same process.

Also you can see below; at the same time range, I am not able to see connection between them on Service Map

If you want to see anything more, just let me know.

[michaelhyatt]

Which version of Elastic stack are you using? What are the configuration options you using for elastic.apm.*?

[alidrsn]

The elastic version is 7.17 from Elastic Cloud. Therefore, there is no specific configuration for elastic.apm*
It is simple as below

java -javaagent:/path/to/elastic-apm-agent-.jar
-Delastic.apm.service_name=my-application
-Delastic.apm.server_urls= "mykibana_URL"
-Delastic.apm.secret_token="MyTOKEN"
-Delastic.apm.environment=production
-Delastic.apm.application_packages=org.example
-jar my-application.jar

[michaelhyatt]

Any chance you can share the sample app for me to test it on my end?

[alidrsn]

Actually, I am not a MuleSoft expert. I am just gathering information from other departments. However, it should be too simple. 2 Mule app + 2 Elastic agent + 1 Http call

[michaelhyatt]

No worries, do you know if it is a Mule domain app, or two standalone apps? Are they using Mule's HTTP client and listener? Also, what version of Mule runtime they are using?

[alidrsn]

What I got from the team is
"
Two standalone apps,
Mule HTTP listener to expose the interface and HTTP Request to make a request to Mule API.
Mule 4 runtime
"

[michaelhyatt]

Both projects Mule 4? Mule 4 agent doesn't support distributed tracing.

BTW, this repo is for Mule 3 agent which does support it.

[alidrsn]

Yes, they are both Mule 4.
Therefore, I noticed that I created this issue on wrong agent (it should be apm-mule4-agent), sorry for that.
However, still need to make it a little bit clear. I can see the transactions with same traceID, belong to two different services.
If it is not supported, how can it be in this case ?

[michaelhyatt]

It shouldn't be the case since there is no support for distributed tracing in the Mule4 agent. It will be good to get a hold of the sample app to test it locally, hard to troubleshoot simply based on images.

[alidrsn]

Thanks for your help and time. I am looking forward to hear from you any update.