Apache agent needs multiple restarts to connect
There are multiple Apache instances on a few machines in our environment. When restarting the instance, it usually takes 2 restarts to finally connect to Dynatrace. The apache configs were not done with the master/slave configuration, but they all were done separate UDP ports. Is this problem related to the configuration?
Also, another reported problem of this team is that they have configured an agent with one name and it shows in Dynatrace the first time they connect. Later on, they will restart and the agent won't connect. They then will slightly alter the name of the agent (i.e. add -test to the end of the name), and the newly named agent will show in Dynatrace. Not sure why this is happening either, but wondering if it has to do with their config as well.
Can anyone shed any light on these issues?
I had the same experience with some Apache agents, installed on the AWS.
It always took two restarts to get them to connect, in that case we also had PHP instrumented with the Apache, some clarification on this would be great.
Ours are Java based applications. I'm concerned because they have automated restart scripts and if they run those, our agents may not come back. I'm wondering if anyone has fixed this problem before or has just dealt with it.
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
