In case Plumbr application detection has detected two or more applications where in reality there is just one, you can merge the applications with the same software into a single application. There are two ways to do this.
You can merge applications via the user interface by renaming one or more applications to bear the same name. For example, applications http://billing.com and https://billing.com might be detected by Plumbr. If you wish to make sure the transactions accessing the billing.com domain are linked to the same application, regardless of whether or not it was accessed over HTTP or HTTPS, you can do just that. Proceed to rename both applications in UI to Billing Live. After this change, previous interactions with these applications will also refer to Billing Live.
In situations where you have several applications to merge, this approach might not be the best choice due to the sheer amount of rename operations involved. This can for example happen in situations where you are exposing your application dedicated to a virtual host to different clients. In such a case, instead of accessing http://billing.com, each client has its unique virtual host (http://company1.billing.com, http://company2.billing.com, etc).
Faced with this situation, you can merge applications via a configuration in the plumbr.properties file located next to the Plumbr Java Agent. You can use this file to modify (or add, if not present) the parameter appId, referring to the identity of the application you wish to use, similarly to the following example:
This change will only be applied to new transactions arriving after the change. All existing transactions will still refer to previous applications.