Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Collector Group for Appmon Agent (one agent)


Hi All,

We will migrate some of our appmon Classic agent to the new appmon 7.2 agents. We will have both classic and appmon agents coexisting for a while in our environnement.

Are there recommendations or best pratices specifically for the new Appmon agent in regard to collector deployement strategies besides the ones from the link below ? Can we have a collector group used by the classic appmon and the new appmon agent ? should we deploy new collectors specifically for the new appmon agents ? Anyone has experience with this kind of scenario ?

Thanks in advance for any inputs


DynaMight Leader
DynaMight Leader

There are no problems with mixing Appmon and classic agents. After migrating all agents to Appmon agents I suggest check if collector groups are needed. For Appmon agent collector is working only as proxy. Instrumentation is on agent side not collector side. Communication is REST not tcp.



Thanks Sebastian,

What about the sizing ? Are the collectors able to support the same total amount of agents (appmon and classic) ? Are the collector specifications different for the appmon agent ?

If we convert and redirect all of our agents (500+) to central collectors, we will need to reevaluate our sizing.

If your sizing was done for classic agent it will work for mixed Appmon and classic as well. After converting to Appmon agent collector is working similar to environment active gate in Dynatrace. It is only proxy. For classic collector is responsible for instrumentation and purepaths building. This is why classic agent needs more power 🙂

Makes sense, thanks a lot for the help!