MySql dependency tree not available with applicationinsights-agent-3.5.1

[abhikt48]

Expected behavior

1. Mule 4 --> MySql dependency should be available in Application Insight (AI).
2. Java --> End to End transaction should be available for multiple transports (MySQL + Mongo) . This is very less priority for us, just FYI, observed while testing.

Actual behavior

We need to use Mule 4 application to log all logs in Application Insight. As part of testing, we discoverd that MySql dependency is not available in AI, however mongo DB dependency is available. Please refer below image where there is no MySql dependency, dependency is not available without transaction ID as well.

Just for replication, I did testing with plain java code and found that both (MySQL and Mongo) dependencies are available in AI. But there is no End To End transaction. Which is quite strange.

To Reproduce

1. Java - Refer this repo to replicate java-ai-db-test
2. Mule - Refer this repo to replicate mule4-ai-db-test

I am not sure, how much comfortable you all with Mule 4. However you can run dependency tree or check if anything is missing in POM.

System information

Please provide the following information:

• SDK Version: applicationinsights-agent-3.5.1
• OS type and version: Windows 11
• Application Server type and version (if applicable):
• Using spring-boot? : No
• Additional relevant libraries (with version, if applicable): Mule Server 4.6.1

Please check above information and let me know for any concern.

[abhikt48]

Can anyone please take a look on this issue ?

[trask]

hi @abhikt48, I don't have any good ideas about this, can you enable self-diagnostic logging at TRACE level and attach the applicationinsights.log from the failure case?

[abhikt48]

@trask I have uploaded logs here applicationinsights.log , could you please check on this.

[trask]

hi @abhikt48,

since the MySql (jdbc) calls are hidden inside of Mule, it's hard to know if Mule is maybe using some jdbc api that's not instrumented, e.g. open-telemetry/opentelemetry-java-instrumentation#4476

[abhikt48]

Closing this issue, as we are focusing on MsSql. So we will track this issue here - #3736