zoomingrocket

@glxorlando - Explore Custom Instrumentation Hook if you know the entry package.method for WSO2, this will help you start capturing proper spans Look at #2048 for more details and it...

@glxorlando - Reading this article https://medium.com/@raj10x/monitor-wso2-products-using-appdynamics-8faf72e83a7, for WSO2 Custom POJO entry point is “org.apache.synapse.core.axis2.SynapseMessageReceive#receive()”

@trask - Thanks for the custom instrumentation hook enhancement with 3.1.1! It's a huge life saver to nail down issues quickly in distributed COTs ecosystem 👍 Now extending the idea...

@trask - Should i be logging a OTEP request or upstream enhancement is tracked differently?

@trask - Thanks, logged similar request in upstream Otel Project - [Otel - 6517](https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/6517 )

We leverage in similar use case with Boomi, and native request correlation works properly. Ensure that between the two Mule APIs you have W3C Trace Headers configured in your API...

@s21-himesh - You can add in your JSON sampling overrides to shut off a particular dependency type. Go through this link for examples - https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-sampling-overrides

@trask - Any feedback on this, is this Otel upstream behavior vs Azure? Is it safe to continue using http.url, or do we need to check if a bug is...

@trask - Thanks, if we switch back to http.url it seems to work for all cases, so it seems like in some cases, upstream Otel semantics are not accurate, possibly.

@trask - Is there an easy way I can extract from either url.full or url.path while setting an attribute? We are setting the extracted attribute as the span name. Since...