Dynatrace Server Crash
Dynatrace Server crashed couple of times in a day and it seems like there was sudden spike in the memory which crashed server. I believe there are some users trying to pull historical data from session but we could not able to trace it back who did this.
I wonder is there any way to get this information? Any other thoughts to mitigate it?
We had this issue at our client as we expanded the number of applications utilizing dynaTrace increased which resulted in more users accessing dT data through the client which would kill the server. We also had a low memory on the dT server which did not support many clients run simultaneously.
I agree with Chris, upgrading to 6.0 should mitigate this as you will be connecting to the frontend server and not the dT server directly.
Since we upgraded to 6.0 and moved the dT server to a new host with a bumped up memory, I have not seen issues after this.
The problem is we have high number of users uses dynatrace and it was very difficult to identify which one is caused.
We recently migrated to 5.6 and not sure by when we will migrate to 6 at this moment.
If the problem persists, you may want to contact support. There is a diagnostic fixpack for 5.6 which allows verbose logging of this kind of user activity.
I have run into this a few times also. There is no easy way to understand who caused the crash, however you can see who was currently logged into the server by viewing the server log file.
WIth dT 6.0 the user should not be able to bring down the server as they are connceting to the front end server (new separate process) for reporting purposes only. dT 6.0 was just released, there are several features that I am very excited about and my client is upgrading to this release ASAP. dynaTrace 6 Release Notes
