We recently upgraded from 4.2 to 5.5 and I noticed you can no longer delete disconnected Agents from the Agents Overview Dashboard. Is there any way to delete them? We recently decommissioned a couple of applications so I would like to remove the disconnected agents left over from it just to keep the Agents Overview clean.
Answer by Sreerag M. ·
If we don't remove the disconnected agent after 3 days we could use it for agent inventory within DynaTrace.
I think we should have a control on which agents should be removed and which ones should be retained even if they are in disconnected state for more than 3 days.
Something like an option to set a custom status of 'agent removed' rather than leaving it with the same status as any other disconnected agents.
We did a server cut-over for one of our application and all our old servers are still listed in the 5.5 infrastructure view. We are finding it very difficult to check if any of our new servers are offline or not.
I think we cannot say an application is healthy after 3 days when the disconnected agents are removed by DT.
We should be able to report on any offline servers in the Infrastructure view no matter if the agent in the server was inactive for more than 3 days or not.
When we remove an agent we could set the status to 'agent removed' in agent overview so that the system can remove those entries after 3 days or we have an option to remove it if required. Also dynatrace dashboards can avoid reporting on the agents with 'agent removed' status.
-Sreerag
Nordstrom
DECEMBER 12, 10:00 AM GMT / 2:00 PM ET
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 10, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 10, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 10, 4:00 pm CET / 10:00 am ET
Register here