All main flows is comes under one Application

[vamsi-jalli]

The issue is, we try to push the flow statistics to monitor in APM ELK. All main flows comes under one single application. Expected behavior is each application should have corresponding main flows right?

Currently we are using Mule Runtime 4.3.0 and mule4-agent is still this one only. Do we have to update mule4 agent so that it supports 4.3.0. FYI, before 4.3.0 we developed mule applications in 4.2.0 and incorporated this mule agent.

Thanks

[michaelhyatt]

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 tested it. Appreciate if you could give it a try and let me know.

[vamsi-jalli]

Is there possibility to add a feature to have multiple applications in APM per runtime? It is working in Mule4.3.0 same like 4.2.0. Thanks for the reply.

[michaelhyatt]

@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 way to set them apart once they are deployed aside from naming the top-level flows differently.