phpDaemon is a lightweight, event-driven, asynchronous server written in PHP. It is designed to be easy to install and set up, and provides a fast and reliable way to serve PHP applications. phpDaemon is a great choice for sites that need high performance and scalability.
The prerequisites for monitoring phpDaemon with Netdata are to have phpDaemon and Netdata installed on your system.
Netdata auto discovers hundreds of services, and for those it doesn’t turning on manual discovery is a one line configuration. For more information on configuring Netdata for phpDaemon monitoring please read the collector documentation.
You should now see the phpDaemon section on the Overview tab in Netdata Cloud already populated with charts about all the metrics you care about.
Netdata has a public demo space (no login required) where you can explore different monitoring use-cases and get a feel for Netdata.
The number of workers that are alive and running. This metric should be monitored to ensure that there are enough workers running to handle the load of incoming requests. If there are not enough workers, requests may be delayed or not be responded to at all.
The number of workers that are alive and either idle, busy, or in the process of reloading. This metric should be monitored to ensure that the system is not overloading the workers and that there is a good balance between the number of idle and busy workers. If there are too many busy workers, it may indicate that the system is overloaded and needs to be scaled up.
The number of workers that are alive but in a preinit, init, or initialized state. This metric should be monitored to ensure that the system is not underutilizing its resources. If there are too many idle workers, it may indicate that the system is not taking full advantage of its resources and needs to be optimized for higher performance.
The amount of time that the system has been running. This metric should be monitored to ensure that the system is stable and reliable. If the uptime is low, it may indicate that the system is experiencing frequent crashes or disruptions, which can negatively impact performance and availability.