That sounds to me more like monitoring that should be provided on the server side. I don’t see how WordPress could detect this without increasing the load itself.
Hello, thank you for your response. @threadi
Of course, server-side monitoring is also required. However, it may be useful to learn which subsites and users may cause an increase in resource usage.
This should also be visible in server-side monitoring. The processes and their resource usage should be listed there, as well as the request that caused the process (i.e. the URL and therefore the page called up).
The processes and their resource usage should be listed there, as well as the request that caused the process (i.e. the URL and therefore the page called up).
Is there a tool where I can track statistics like this? @threadi
As I said, not with WordPress.
There are many monitoring tools on the server side. However, the analysis you want also requires a lot from the system below, such as being able to trace the process back to its origin. With Linux-based systems, I think this is quite feasible, I’ve already done it manually. A monitoring tool should be able to collect and analyze this data itself. I use Zabbix for this, but have never configured such a task there (even though I think it would be possible). The use of a monitoring tool like Zabbix requires a dedicated server and not simple hosting. But that’s just a small excursion, as I said, it has nothing to do with WordPress.
Thank you very much for your suggestion. @threadi
I will research and try Zabbix and other monitoring tools. In fact, as I mentioned, my only purpose is to find out which subsites cause an increase in resource usage on the server. For this, it is necessary to find out which subsites and pages use how much CPU, RAM and traffic.
Which metrics of subsites do you monitor for such problems? So, what really matters is the CPU, RAM and traffic (bandwidth) used by the subsites, right?
As already mentioned, I do not actively monitor such details myself. If I notice a higher load and the affected website is on a Linux system that I manage, I look directly for the cause myself – if necessary by debugging the process.
Incidentally, you could also approach your problem from a different direction. Deactivate the plugins used by the website and see if this reduces the load. You may also have to wait a few days, depending on the traffic on the site. Of course, this is unfavorable for an actively used live system, but at least you can narrow down the cause without extensive monitoring.
