Dear Support Team,
Hello
You mentioned before that there is not a certain number for sensor counts in XL licenses and that it's related to a lot of things such as sensor types, intervals, APIs, reports, maps, dashboards, number of users, number of probes and etc.
I want to know, despite all these things, what happens if the service overloads? Is it stops? Is it delayed? all or part of sensors becomes unknown?
In other words, how can I be sure that the system has not been overloaded yet and is working properly and the data is correct?
Thanks a lot
What happens if the service overloads?
Votes:
0
1 Reply
Votes:
0
Hello,
indications of an overloaded PRTG core server include:
- Slow web interface
- A lot of grey sensors while the probes are working fine
It is not easy to estimate reliably how much more a core server can take. It can be the case that a large PRTG setup works well with just one user logged in, but has interface lag with 5 users logged in and working.
One sign of overload can be detected in the "core.log", if you search for "LockReason". Those shows you log entries noticing a thread already waiting 60 seconds to get access to an object (which is locked by another thread for data consistency).
A couple of those entries are nothing to worry about, but if you constantly have those, like 100+ a single day, the core server is seriously overloaded. Or if every day some of those lines appear, that should also be checked.
Created on Apr 26, 2021 2:39:38 PM by
Last change on Apr 26, 2021 2:40:27 PM by
Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Add comment