Recently, we tried to run a couple historic data reports. Apparently those jobs were too much for PRTG to handle because it hung for 30-45 minutes. We needed to terminate the jobs because they were using too much CPU. The only way we could come up with to stop those queries was to restart PRTG. Is there another way to do this? If not, could we suggest a feature enhancement that would allow you to terminate queries without restarting the system?

Article Comments

What exactly were you creating the reports for (i.e. number of sensors, time span, etc.)? Depending on the amount of objects and time span selected, generating a particular report can take quite a while.


Apr, 2011 - Permalink

I have this same problem with PRTG 9.2.1.2280. I am trying to run the Review or Download Historic Sensor Data feature within one sensor and it just hangs. The Quad core CPU server went from about 17% to 48%. The popup window that will present the Historic Data review is just blank and waiting. It has ran for over 15 mins and nothing yet.


Apr, 2012 - Permalink