Michael Hyatt

No version, but it should be fairly easy to rebuild the agent with the right version of Mule runtime API jar that works with 4.2.2

@adrianj I created a new release that populates MDC with `trace.id` and `transaction.id`, please give it a go: https://github.com/michaelhyatt/elastic-apm-mule4-agent/releases/tag/v0.0.3

Could it be the AsyncLogger? If not, it may require extending the log4j: ``` Log4j 2.7 adds a flexible mechanism to tag logging statements with context data coming from other...

Hey, I am not too familiar with Azure devops, but you will need to make the `jar` file available for maven to pick it up from somewhere. This is how...

Hi @vamsi-jalli The APM will create one application/service per JVM/Mule runtime and will have different flows represented as transactions. The agent should work as-is with Mule 4.3, but I haven't...

@vamsi-jalli the application name is a design-time construct in Mule, so at runtime, all the deployed projects are sharing the same JVM and the same APM agent. There is no...

This is great. Can you please reach out to my email mhyatt8080 at g mail c om and we'll have a quick chat on zoom. Thanks for reaching out.

Yes, if you are using Mule domain-based projects, the APM agent configuration is done at the domain level and all the Mule domain projects are deployed and running as part...

Check out the sample app https://github.com/michaelhyatt/elastic-apm-mule3-agent/tree/master/example-domain-app Everything is declared in the domain project, so dependant projects can remain tracer agnostic.

Yep, will have a look. Thanks for reporting it.