What to do with alert of "Application Process Unavailable process-x" when agent reconnected as process-x[1]
Hi,
I have a minor annoyance with dynaTrace:
When an agent experience a quick disconnect/reconnect (whether due to a reboot, a crash & automatic recovery or maybe network problems), the agent reconnects and changes name from someProcess:1234 to someProcess[1]:2345. This is not a problem per se, but it causes dynaTrace to consider the original "someProcess:1234" to be down as per the Application Process Unavailable (unexpected) rule. Then follows emails saying that the process has been down for X minutes and then X hours, where it actually was unavailable for a few seconds!
We also need to login in dynaTrace and manually delete the Incident, or it will continue to be an "ongoing" incident...
Has anyone else experienced something similar, how can we solve this problem?
Sincerely,
Alexandre
Follow up: We ended up using -Dcom.dynatrace.diagnostics.collector.agentcenter.unique_agent_names_with_index=false in dtcollector.ini
Hi alexandre.leveille@sunmedia.ca,
I've ran into the same issue a few times. The way I've handled it was by setting the "com.dynatrace.diagnostics.collector.agentcenter.unique_agent_names_with_index" to false. Please look here for more information.
You can enter debug mode with ctrl + shift + f9 and you'll find the debug options on the collector page under dynaTrace server settings. It might be worth opening a ticket still because I'm not sure if this is the best answer but it should at least help out temporarily.
Thanks,
Mike
Thank you Beemer, I'll try that
