Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
Wasagent
Current Version
r182 build
Last Release Date
2012-10-10
Compatible With
- Nagios 3.x
Owner
Website
License
GPL
Hits
108202
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!
Nagios monitoring is achieved with simple HTTP requests, through the use of an embedded Jetty container. The plugin acts as a reverse proxy and thus can be used to monitor as many WebSphere instances as you need.
Current features are:
* JVM heap monitoring
* Server thread pools monitoring, including hung thread detection
* JTA transactions monitoring
* JDBC datasources monitoring
* JMS connection factories monitoring
* JMS 1.0 listeners status monitoring
* SIB queues depth monitoring
* HTTP sessions monitoring
* Clustering support
* Administrative security support
* JVM heap monitoring
* Server thread pools monitoring, including hung thread detection
* JTA transactions monitoring
* JDBC datasources monitoring
* JMS connection factories monitoring
* JMS 1.0 listeners status monitoring
* SIB queues depth monitoring
* HTTP sessions monitoring
* Clustering support
* Administrative security support
Reviews (2)
Works on WAS 8.5 after using IBM jdk 6.
By default, ssl for soap must be used.
Keys (*.p12) are located in WAS install directory (you can search them and copy in plugin direcory).
Password for keys are: WebAS
If something goes wrong remove redirection (wasagent.sh) to dev-null to see errors.
When config is changed kill daemon (run.sh) and start again. Documentation should be better.
By default, ssl for soap must be used.
Keys (*.p12) are located in WAS install directory (you can search them and copy in plugin direcory).
Password for keys are: WebAS
If something goes wrong remove redirection (wasagent.sh) to dev-null to see errors.
When config is changed kill daemon (run.sh) and start again. Documentation should be better.
I appreciate your work for this plug-in...
