Monitoring via Direct TCP/IP (No External Commands/Plugins)

[eloyd]

I still think it's a development effort either way and the OP must decide what's going to be the best bang for the buck and how many minute hand sweeps he wants to watch go by while waiting for it to get done.

Either way, I think it's beyond the scope of this forum.

[abrist]

True enough. My suggestion will still be to use check_jmx as I would rather have my servers do more work than myself
OP: Can I lock this?

[janaka]

Thanks @eloyd, @tmcdonald, @abrist!

Write a daemon that does your checking by maintaining an established connection. Run this thing on your Nagios host. Give IT the ability to respond to HTTP requests which you can then query from Nagios in the usual manner. So in essence, you're monitoring a monitoring process.

I finally ended up implementing something similar; a TCP client that maintains a persistent connection to a JMX query handling agent on my remote server, and writes back the query responses as passive monitoring commands into the Nagios external command file (pipe). Currently I can live with that implementation, at the expected level of performance and monitoring detail.

I will catch up with you guys if I happen to need to dig deeper.
Thanks again!

[janaka]

OP: Can I lock this?

Sure, thanks!

[eloyd]

Love the implementation!

[tmcdonald]

Going to lock this now, but please PM one of the moderators if you want it re-opened.