Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
perfservmon
Current Version
1.5.1
Last Release Date
2018-08-09
Compatible With
- Nagios 3.x
- Nagios 4.x
Owner
License
MIT
Hits
8398
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
Sample Checks
First run the following check to collect the perfservlet data from WAS Cell WAS_Cell_name:
Nagios Path/libexec/perfservmon.py -C WAS_Cell_name retrieve -N Perfservlet_Host -P Perfservlet_Port
Optionally in case you use https and/or basic auth credentials to connect to Perfservlet Application run the following check:
Nagios_Path/libexec/perfservmon.py -C WAS_Cell_name retrieve -N Perfservlet_Host -P Perfservlet_Port -H https [ --ignorecert ] -u userid -p passwd
You may want to perform the check above with a custom interval(e.g. 3 minutes) to collect fresh data from Cell.
Then add Monitoring Checks like the following:
- Check the Total live http sessions of Servlets of the Server ServerName, get critical alert when 10000, warning when 5000.
Nagios Path/libexec/perfservmon.py -C WAS_Cell_name show -n NodeName -s ServerName -M LiveSessions -c 10000 -w 5000
-Check the usage of WebContainer Thread Pool of Server ServerName, get critical alert when over 90%, warning when over 70%.
Nagios Path/libexec/perfservmon.py -C WAS_Cell_name show -n NodeName -s ServerName -M WebContainer -c 90 -w 70
-Check the JVM Heap usage of Server ServerName, get critical alert when over 90%, warning when over 70%.
Nagios Path/libexec/perfservmon.py -C WAS_Cell_name show -n NodeName -s ServerName -M Heap -c 90 -w 70
-Check the usage of the Connection Pools available for Server ServerName, get critical alert when over 90%, warning when over 70%.
Nagios Path/libexec/perfservmon.py -C WAS_Cell_name show -n NodeName -s ServerName -M DBConnectionPoolPercentUsed -c 90 -w 70
First run the following check to collect the perfservlet data from WAS Cell WAS_Cell_name:
Nagios Path/libexec/perfservmon.py -C WAS_Cell_name retrieve -N Perfservlet_Host -P Perfservlet_Port
Optionally in case you use https and/or basic auth credentials to connect to Perfservlet Application run the following check:
Nagios_Path/libexec/perfservmon.py -C WAS_Cell_name retrieve -N Perfservlet_Host -P Perfservlet_Port -H https [ --ignorecert ] -u userid -p passwd
You may want to perform the check above with a custom interval(e.g. 3 minutes) to collect fresh data from Cell.
Then add Monitoring Checks like the following:
- Check the Total live http sessions of Servlets of the Server ServerName, get critical alert when 10000, warning when 5000.
Nagios Path/libexec/perfservmon.py -C WAS_Cell_name show -n NodeName -s ServerName -M LiveSessions -c 10000 -w 5000
-Check the usage of WebContainer Thread Pool of Server ServerName, get critical alert when over 90%, warning when over 70%.
Nagios Path/libexec/perfservmon.py -C WAS_Cell_name show -n NodeName -s ServerName -M WebContainer -c 90 -w 70
-Check the JVM Heap usage of Server ServerName, get critical alert when over 90%, warning when over 70%.
Nagios Path/libexec/perfservmon.py -C WAS_Cell_name show -n NodeName -s ServerName -M Heap -c 90 -w 70
-Check the usage of the Connection Pools available for Server ServerName, get critical alert when over 90%, warning when over 70%.
Nagios Path/libexec/perfservmon.py -C WAS_Cell_name show -n NodeName -s ServerName -M DBConnectionPoolPercentUsed -c 90 -w 70
Reviews (0)
Be the first to review this listing!
