.NET Worker Processes Alerting Constantly
Hello,
In the past I worked with support regarding .NET worker processes automatically shutting themselves down in low-load situations (this is normal .NET behavior).
Unfortunately dynaTrace 5.5 records this as an agent disconnection event. and this causes 2 problems for us:
1) dynaTrace Alerts our operations teams. Is there a way to disable these alerts for a given agent group?
2) It's also common that the agent will actually wake back up before the shut down event is processed. When this happens we see the following:
10:40.30pm .NetAgent01[1] has connected
10:40.31pm .NetAgent01 has disconnected
This happens when the worker process disconnected but dynaTrace does not have time to record this event before it comes back and registers as a second agent.
Both the alerting and the clustering is causing difficulty troubleshooting. Has anyone else experienced this before? What are the best practices in dealing with this issue?
In your case i think a higher evaluation time-frame will work, but these are our of the box incidents and we cannot modify those.
Here is an RFE requesting ability to modify those out of the box incidents. please vote if you find useful. Enhancement Request - Ability to modify evaluation timeframe for built-in incidents
-Sreerag
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! 