Collector configuration
This question is related to the setting in the dynaTrace Server -> Services (General Tab).
Where I work we have a pretty simple dynaTrace 5 installation meaning we don't have that many agents connected and usually will troubleshoot some issue with a team, disable profile to release agent license, and move on to another team that requires help with their application. We have tons of applications we support. The dynaTrace server is on the same server as the dynaTrace client and collector.
With that said, can we use the option "Allow Agent Connections to dynaTrace Server"? What is the point of using a collector if it's on the same box as the server. And on top of that we never have more than 5 agents connected and no more than 2 profiles active.
Right now it's actually unchecked but wondering if I should probably check it...which is the default setting after install.
Thank you!
Dan
Hi Dan,
My recommendation would be to always use a separate collector rather than the in-process one you can enable with that option.
Reasons are that when the dynaTrace server runs into a major GC or comes under heavy load because a lot of analyzer threads are triggered by users you still have the collector to accept data from incoming agents, allow new agents to connect and so on.
The number of agents can be low - it is how much transactions they produce that is the key factor if the embedded collector works or not.
What's your concern here - we do install the out-of-process collector automatically, so it's just another service to start and one option (amongst many) to change in the server settings after install...
Best, Roman
