This update of xymonq adds the possibility to prefix the results with the hostname. The -S-option (that added the line HOST=<hostname> above the results) is deprecated as it made parsing needlessly difficult.

An example of the old behaviour:

$ xymonq -H google.com -q xymondlog -T http
www.google.com|http|green||1516618364|1516956137|1516957937|0|0|127.0.0.1||||N|
green Fri Jan 26 09:42:16 2018: OK ; OK

&green http://google.com/ - OK

Adding -p prefixes the output with the hostname:

$ xymonq -H google.com -q xymondlog -T http -p
www.google.com: www.google.com|http|green||1516618364|1516956137|1516957937|0|0|127.0.0.1||||N|
www.google.com: green Fri Jan 26 09:42:16 2018: OK ; OK
www.google.com:
www.google.com: &green http://google.com/ - OK

The (now deprecated) -S option produced harder to parse output:

$ xymonq -H google.com -q xymondlog -T http -S
HOST=www.google.com
www.google.com|http|green||1516618364|1516956137|1516957937|0|0|127.0.0.1||||N|
green Fri Jan 26 09:42:16 2018: OK ; OK

&green http://google.com/ - OK

For more details see the project-page: xymonq.

This update of xymonq fixes a bug introduced in v0.6 with handling the config-file: The default-locations were not searched any more.

In addition the listing of available sections for clientlog now shows all available sections and not only ones matching [[:alnum:]].

For more details see the project-page: xymonq.

This update of xymonq brings

  • new querytype config: Fetch files from the xymon-server. The restrictions of xymon apply (only files from the server/etc/-dir, only .cfg-files).

  • specify a config-file with -c conf-file in addition to the default search machanism.

  • allow more default-values to be set in config-file (TEST, FIELDS, SECTION)

  • help/documentation improvements

For more details see the project-page: xymonq.

This update of shorewall-monitor for Xymon fixes an undetected state-error.

The shorewall status command returns 2 states. In the following example everything is fine — is stopped and State:Cleared are in sync:

# shorewall status
Shorewall-4.5.5.3 Status at my-host - Sun Nov 12 13:30:03 CET 2017

Shorewall is stopped
State:Cleared (Sun Nov 12 13:29:54 CET 2017)

The following output might be returned after a reboot:

# shorewall status
Shorewall-4.5.5.3 Status at my-host - Sun Nov 12 13:30:15 CET 2017

Shorewall is stopped
State:Started (Sun Nov 12 13:29:38 CET 2017) from /etc/shorewall/

Note that is stopped and State:Started are not consistent. The latter is fetched from a state-file, that is not removed/reliably updated.

This behaviour was discoverd in Debian Wheezy with the shorewall-lite packages from the official Debian repository.

Prior to v0.7 shorewall-monitor exclusively checked the State:xxx-line. Starting with v0.7 the status goes red in case the two states are not in sync.

For more details see the project-page: shorewall-monitor for Xymon.

This update of xymonq brings

  • new querytype hostinfo: print a parsable representation of the configuration from hosts.cfg for the selected host(s)

  • help/documentation improvements

For more details see the project-page: xymonq.

Xymon does out-of-the-box monitoring of SSL-certificates. So for any SSL-enabled service that is checked (https, pop3s, imaps, ldaps, …1) by default the certificate is checked too and the result is shown in a separate status sslcert. For SNI (Server Name Indication)2 enabled services extra care is required.

In the previous article on Agent-less Monitoring With Xymon Using xymon-rclient a basic monitoring setup of a QNap NAS appliance was shown. As promised here is the follow-up on the BusyBox-specific adjustments to get more metrics “right”. As a bonus an issue with RAID-monitoring on QNap is addressed to prevent false positives in Xymon. The resulting client-script is usable with other BusyBox-based systems and is in use with UniFi WLAN Access Points from Ubiquiti Networks.

Xymon is an agent-based1 monitoring solution. That means that a xymon-client is installed on the monitored system. For an unixoide OS hat client collects various metrics via a simple shell script and sends that data to the Xymon server using the xymon-binary2 with a simple clear-text protocol.

On some systems it is not possible for technical (no installation permissions, client not available, no compile environment) or legal (appliance vendors often forbid installing 3rd party applications) reasons to install the xymon client.

But these systems often have remote access possibilities — nowadays mostly SSH. In that case these can be monitored anyway using the server-side extension xymon-rclient3. This article describes the setup using QNap NAS appliances and SSH for remote access as an example.

This update of xymonq brings new querytypes for

  • ghostlist: including filtering for the repoting-time. To show ghosts reported within the last 10 minutes use:

      xymonq -q ghostlist -a "10 minutes ago"
    
  • ping|version: to query the version of the Xymon server xymonq is talking to

      xymonq -q ping
    

A config file has been added to specify the path to the xymon binary and the connection to the Xymon server (IP:PORT). It also allows to configure a default QUERYTYPE to probably save some typing.

For more details see the project-page: xymonq.