Sznick, Victor, Carls
RE: Monitoring Daemon Processes
As you're already aware of, a daemon in the Unix world, is what a Service is in the Windows world. We can monitor either of these by deploying the “Process Count Check” monitor against a given server. Simple add the service, specify a name, select a host, enter the process name and select a comparison method for the response time and process occurrence.
RE: Apache Tomcat Plug-In Monitor
Angelo posted an Apache Tomcat plug-in monitor, to our Forums, earlier this year. I've included the details from his post below, for your convenience:
Purpose
Provides basic monitoring of Tomcat server performance.
Description
This plug-in monitor collects statistics from your Tomcat server including memory, thread, and data rate statistics. You can then set alerts based on pre-defined thresholds.
This monitor gathers the following statistics from the Tomcat Server:
* Maximum JVM memory
* Total JVM memory
* Thread count
* Current busy thread count for the connector
* Max number of threads for the connector
* Number of bytes received by the connector
* Number of bytes sent by the connector
* Number of errors for the connector
* Number of requests for the connector
* Processing time for the connector
Requirements
Monitoring station
up.time version – v4 or greater
Dependencies – None
Installation
Windows
* Install the downloaded plug-in monitor using loadpluginmonitor.exe
On the command line, run loadpluginmonitor.exe (found in the scripts directory), providing the absolute path to the downloaded plug-in monitor.
e.g.: loadpluginmonitor c:Program Filesuptime softwareuptime4scriptstomcat_windows.zip
or scriptsloadpluginmonitor c:tomcat_windows.zip
Running loadpluginmonitor unarchives the plug-in monitor contents to the appropriate up.time /script and /xml directories (and if applicable, /agent and /lib directories), and will add the plug-in monitor to the up.time interface (specifically, the Advanced Monitors section of the Add Service Monitor page).
UNIX
* Install the downloaded plug-in monitor using loadpluginmonitor
On the command line, run loadpluginmonitor (found in the /scripts directory), providing the absolute path to the downloaded plug-in monitor.
e.g.: loadpluginmonitor/usr/local/uptime4/scripts/tomcat_unix.zip
or /scripts/loadpluginmonitor/user/local/tomcat_unix.zip
Running loadpluginmonitor unarchives the plug-in monitor contents into the appropriate up.time /script and /xml directories (and if applicable, /agent and /lib directories), and will add the plug-in monitor to the up.time interface (specifically, the Advanced Monitors section of the Add Service Monitor page).
Configuring the Monitor in up.time
The following configuration settings need to be set when creating a service instance based on this plug-in monitor:
* Script Name – the name and location (on the monitoring station) of the script that runs the JAR, which in turn connects to the Tomcat Server
* Manager URL – the URL to the Tomcat management console
* Manager Port – the port of the Tomcat management console
* Manager Password – the password required to access the Tomcat management console
The following metrics are used to set alerting thresholds, and can be included in Report graphs:
* Max Memory – Maximum JVM memory
* Total Memory – Total JVM memory
* Thread Count – Current thread count for the connector
* Threads Busy – Current busy thread count for the connector
* Max Threads – Maximum number of threads for the connector
* Bytes Received – Number of bytes received by the connector
* Bytes Sent – Number of bytes sent by the connector
* Request Count – Number of connections for the connector
* Max Time – Maximum request processing time for the connector
* Processing Time – Processing time for the connector
The windows and UNIX based plugin can be found in our Forums.
Regards,