Analyse the Tomcat status page
This plugin does a HTTP GET of the tomcat status page:
/manager/status?XML=true
It checks the resulting XML for:
* Low free memory
* Excessive thread usage
Note that although this sounds quite useful, the nature of garbage collection
in Java means that this plugin is prone to 'false positives' when reporting
memory usage. IE: it will complain about low memory, which may be fixed by the
next garbage collection.
I suggest setting the critical threshold for memory quite low - 50 Mbytes or
less.
It is also useful to set the 'max_check_attempts' higher than usual to give
garbage collection time to kick in.
This plugin has proved useful in debugging, by picking up when a problem
started, as distinct from when the tomcat actually failed.
- Links to server:monitoring / monitoring...ins-tomcat
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:interstar001:Monitoringplugins/monitoring-plugins-tomcat && cd $_
- Create Badge
Source Files (show unmerged sources)
Filename | Size | Changed |
---|---|---|
13-03-15_12-09-48_check_tomcat.pl | 0000013194 12.9 KB | |
gpl-3.0.txt | 0000035147 34.3 KB | |
monitoring-plugins-tomcat.changes | 0000000323 323 Bytes | |
monitoring-plugins-tomcat.spec | 0000002562 2.5 KB |
Comments 0