Supervisor is a client/server system that allows its users to monitor and control a number of processes on UNIX-like operating systems.
The prerequisites for monitoring Supervisord with Netdata are to have Supervisord 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 Supervisord monitoring please read the collector documentation.
You should now see the Supervisord 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.
Summary Processes is a metric that allows users to monitor the number of processes that are running and non-running in the system. It is important to monitor this metric because it can provide insight into system performance, resource utilization, and potential issues that could be impacting the system. When monitoring this metric, it is important to look for any significant changes or discrepancies between the number of running and non-running processes as these could indicate problems with the system or processes that need to be addressed.
Processes is a metric that allows users to monitor the number of processes running and non-running for each process group. This is especially important for systems with multiple process groups running simultaneously, as it can be used to identify potential issues with any of the process groups. It is important to monitor this metric to ensure that all process groups are running as expected and that there is adequate system resources being allocated to each process group.
Process State Code is a metric that allows users to track the state of each process within the system. This metric is important to monitor as it can provide insight into the health and performance of each process. It is important to look for any changes in the code, as this may indicate that a process is not running as expected or that an issue is occurring with the process.
Process Exit Status is a metric that allows users to track the exit status of each process within the system. This metric is important to monitor as it can provide insight into the success or failure of each process, as well as any potential issues that could be impacting the process. It is important to look for any changes in the exit status, as this may indicate that a process is not running as expected or that an issue is occurring with the process.
Process Uptime is a metric that allows users to monitor the amount of time each process has been running. This is important to monitor as it can provide insight into the performance of each process, as well as any potential issues that could be impacting the process. It is important to look for any changes in the uptime, as this may indicate that a process is not running as expected or that an issue is occurring with the process.
Process Downtime is a metric that allows users to monitor the amount of time each process has been non-running. This is important to monitor as it can provide insight into the performance of each process, as well as any potential issues that could be impacting the process. It is important to look for any changes in the downtime, as this may indicate that a process is not running as expected or that an issue is occurring with the process.