Nagios XI - JBOSS Monitoring

[sify_nagios]

Hi Team,

I would like to explore monitoring parameters i can configure for the JBOSS in Nagios XI.
Kindly provide us the list of parameter can be configured.

Please provide us the list of possible parameter list.

Note : Had a look at the 3 plugin in https://exchange.nagios.org/directory/P ... vers/JBOSS.
They failed to educate me on what parameters can be monitored.

Guide us on the same.

Rgds
Srini

[bwallace]

Perhaps it may be more efficient if you let us know what you'd like to monitor specifically.
Regarding plugins, keep in mind that most of what you find at the exchange site are are not written by Nagios nor does Nagios maintain the plugins. The 'check_jboss_status' has a decent usage description / example. Have you tried this plugin?

Usage: check_jboss_status.pl [-H ] [-P ] [-t ]
[-m ] [-a ]
[-h ]
-H The host to connect to (default: localhost)
-P The port to connect to (default: 8080)
-a The AJP ports to check for (default: 8009)
-h The HTTP ports to check for (default: 8080,8443)
-t The percentage of threads busy for warning
(default: 80,50)
-m The percentage of memory used for warning
(default: 80,50)

Example:
check_jboss_status.pl -H jboss.example.com -P 8080 -t 90,75 -m 75,50 -a 8009 -h
8080,8443
This will check the host "jboss.example.com" on port "8080" and
issue a warning at 75% thread busy or a critical alert at 90% thread
usage, or a warning at 50% or critical at 75% JVM memory usage checking.
for AJP port 8009 and HTTP ports 8080 and 8443.


'In-depth checks for JBoss Java EE Server' has a great description and example here, did you check this out?
http://jboss2nagios.sourceforge.net/

Retrieve some MBean attribute value from a JBoss server through the collector MBean:
check_mbean_collector -H host -p port -m mbean_name -a attribute_name -w warning_level -c critical_level

check_mbean_collector -H host[,host,..] -p port -m mbean-name -a attribute-name -w warning-level -c critical-level
check_mbean_collector [-h | --help]
check_mbean_collector [-V | --version]

<host> The server running JBoss.
Giving a comma separated list of hosts switches to a check for a singleton in a cluster.
<port> The port the deployed collector MBean is listening to
<mbean_name> The JMX name of the MBean that includes the attribute, e.g. jboss.system:type=ServerInfo
Use the ${some.env} notation to refer to a JVM system property on the server.
In Nagios config files this must be escaped like this: $$\\{some.env}
If there's a space in the MBean name use a + instead of the space.
<attribute_name> The name of the MBean attribute to retrieve, e.g. ActiveThreadCount
For attributes which are collections the number of entries can be checked by
appending [] to the attribute name.
Prefix the attribute name with a * to get the difference between two calls (delta).
${some.env} can be used (see mbean_name).
<warning_level> The level as a number from which on the WARNING status should be set
<critical_level> The level as a number from which on the CRITICAL status should be set
If you are checking an attribute that is not a Number the specified text will raise the
specific level if it can be found in the textual representation of the attribute
For specifying ranges or 'less than' triggers use the Nagios range notation
(see http://nagiosplug.sourceforge.net/devel ... HOLDFORMAT)