[Xymon] Xymon script for linux

Bruce Ferrell bferrell at baywinds.org
Sat Sep 21 02:30:35 CEST 2019


I'm curious how you propose actually using sar data in a client message.  On my system /var/log/sa is 44M of text data.

vmstat (procps) is already used and feeds rrd on the server via the client message; which is a MUCH more compact, long term storage format (The rrds for the same system are only 13M).

The perennially discussed issues around parsing iproute2 output are kind of well cpovered so we'll let that be... And no, SUSE hasn't removed net-tools.  It's just not installed in 
a very minimal install.



On 9/19/19 7:53 PM, Jeremy Laidman wrote:
> Would it be difficult to have the server-side linux parser look for [ports] and if not found, then look for [ss]; and similarly, [ifconfig] has [ip-addr] as its fallback 
> (assuming "ip addr show" gives similar output - probably doesn't, but you get the idea)?
>
> Minorly tangential, I think sar is more universally available these days than when the client scripts were first created. So I'm wondering if we should make better use of sar, 
> perhaps even have a [sar] section of the client message, that is the first place that xymond goes when looking for statistics.
>
> On Fri, 20 Sep 2019 at 00:52, Japheth Cleaver <cleaver at terabithia.org <mailto:cleaver at terabithia.org>> wrote:
>
>     On 9/18/2019 8:05 AM, Zdeněk Tlustý wrote:
>     > Hello,
>     >
>     > the script xymonclient-linux.sh is using commands like ifconfig,
>     > netstat, etc. These commands are marked as depreciated and some of the
>     > Linux distributions have removed them already. For example SuSE Linux
>     > Enterprise Server 15 has no support for netstat and ifconfig.
>     > The replacement are commands from iproute2 package like ip, ss,
>     > routel, etc.
>     > Are there any plan to replace depreciated commands with new ones?
>
>
>     Especially with SS and IP, it's something that's on the road map.
>     Unfortunately, doing that in a backwards-compatible way will still
>     keeping the 'linux' OStype/class 'linux' might prove difficult without a
>     lot more text processing. (This flag is split on the receiving side for
>     parsing out what client evaluations to run and how, since the output of
>     SunOS, Linux, BSDs, and other *nixes can vary widely.)
>
>     One could either move current OS's to something like "linux-old", or
>     have upgraded scripts under "linux-new", or do a lot of 'awk' calls in
>     xymonclient-linux.sh to try to duplicate previous output more precisely.
>     I'm not sure which is better there.
>
>     Regards,
>     -jc
>
>     _______________________________________________
>     Xymon mailing list
>     Xymon at xymon.com <mailto:Xymon at xymon.com>
>     http://lists.xymon.com/mailman/listinfo/xymon
>
>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon




More information about the Xymon mailing list