Nagios Support Forum

I would like to monitor below jboss metrics in nagios


Heap size
Non-heap size
Thread pool count
Datasource connection
And so on.

Let me know what are the changes we need to do on jboss end and from. Nagios end.

Regards,
Mohan

Here is our guide for using check_jmx:

https://assets.nagios.com/downloads/nag ... ios-XI.pdf

Here are some other Jboss plugins:

https://exchange.nagios.org/directory/P ... vers/JBOSS

Here is another one:

https://developer.jboss.org/wiki/JBossNagiosPlugin

We can help you get things working from the Nagios end but you will need to work with your Jboss admins to get them working, we are not Jboss admins here.

I also found this that has other instructions for your Jboss admins:

http://jboss2nagios.sourceforge.net/

I want to monitor jboss version of 7. Can we be able to monitor jboss 7 in nagios.

Ijust wanted to monitor below paramenters for jboss7.

jvm heap usage
web container threads being used
connection pool size

Above provided plugin is jmx metrics which is not actual jboss plugin

Are you running JBoss AS 7.1.1.Final?

some jboss are version 7 and some are 7.1.1 . let me know the suitable plugin that we can use for actual jvm metrics for both jboss7 and jboss 7.1.1 . I can see plugin link provided above supports only JBoss standalone mode. But we have multiple jvm instances running on same server. we need to monitor each of the jvm instances from nagios.

Im trying to use python plugin and im getting below error which is not working

CRITICAL - JbossAS Error: Expecting value: line 1 column 1 (char 0)

Please post the exact plugin (or a link to it) and the exact command you are using with the full output so that we can debug further.

Thank you

Here is the link to plugin and im attaching script as well .

https://github.com/aparnachaudhary/nagi ... n-jbossas7

below is the command I have used .

./check_jbossas7.py -H 'hostname' -A threading -P 'PortNumber'-u username -p password -t thread-count -W 80 -C 90 -D

It looks like this can fail with basic connectivity issues. I would verify the IP address and port are accessible from the machine where this plugin is running:

telnet <hostname> <PortNumber>

The credentials could also cause a problem if there are any special characters that the command line is interpreting. Try putting the username and password in quotes.

Finally, a tcpdump can shed some light on this:

tcpdump -s 0 -i any port <PortNumber> -w output.pcap

Let this run just long enough to reproduce the error and use CTRL+C to stop it. The output.pcap can be reviewed with wireshark. Please PM it to me and @Nagios Support if you would like us to review it.