Hi Adam,
On 1/3/26 2:06 PM, Adam Thorn via Xymon wrote:
Extension scripts (whether client-side or server-side) just send a message to your xymon server saying "$TESTNAME has colour $COLOUR, message $MESSAGE etc". Look in "man xymon" under "XYMON MESSAGE SYNTAX", for the message-type of "status"
I'm fairly familiar with client side extensionis. I've created half a dozen or more and am quite happy with them.
separately there's the suite of reports sent by /usr/lib/xymon/client/ bin/xymonclient-linux.sh (or other similar scripts in that directory for other OSs). Run the script manually, and it'll just print a wall of text divided into sections with headers like [date], [uname] etc . When run by xymonclient.sh , that gets sent to your xymon server where it's parsed, with the resulting colours being determined by the contents of your analysis.cfg .
I think I understand that process.
I've got some AIX systems that I've gotten to send status (output from xymonclient-aix.sh) via a wrapper script that's called by cron. I went that route because I don't yet have a compile of Xymon for AIX.
I've recently gotten my hands on a non-production system that I will be installing the GNU toolchain so that I can compile Xymon on AIX. That will allow me to utilize some of the file monitor checks.
Those functions generally finish by sending a suitable "status" message to the xymon server, just like an extension script does when you call $bb->send().
Hum.
Are you suggesting that the Xymon server receives the xymonclient-${OS}.sh script output, processes it, and then turns around and sends status updates the same way that I can use xymonclient to send status updates? -- I naively assumed that it would send them internally via some sort of RPC and not externally.
Possible note of caution: by default, clear-coloured messages don't lead to alerts. See the value of ALERTCOLORS in your xymonserver.cfg , which defaults to red, yellow, purple. Yes, I'm aware. I'm relying on analysis.cfg DS config stanzas to set the color as necessary per host.
The extension sends clear to be generic and able to run across systems. Then each HOST has a proper DS setting for that host.
HOST=host1.example.net DS sendmailq sendmailq.rrd:mqueue >25 COLOR=yellow "TEXT=There are &V messages in the mqueue queue (&L / &U)."
HOST=host2.example.net DS sendmailq sendmailq.rrd:mqueue >5 COLOR=yellow "TEXT=There are &V messages in the mqueue queue (&L / &U)."
That way host1 warns when there are more than 25 messages in the mail queue and host2 warns when there are more than 5 messages in the mail queue. The same script is used to collect data, send a clear message with details.
This has been working great!
Did I miss information about how to get TLS certificate information from my custom server extension to show up on the sslcert page?
I can easily create a script to do the testing, but I don't know how to pass TLS cert details so that they show up on the sslcert page.
-- Grant. . . .