<div dir="ltr"><div dir="ltr">On Sat, 21 Sep 2019 at 10:30, Bruce Ferrell <<a href="mailto:bferrell@baywinds.org">bferrell@baywinds.org</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
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.<br></blockquote><div><br></div><div>Yeah, I could have been clearer in describing what I had in mind.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
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).<br></blockquote><div><br></div><div>
If "sar [some options]" can produce equivalent output to (say) "vmstat 300 2", then it's likely to take the same amount of storage and bytes transmitted. But it has the added benefit that the same sar output from Solaris and AIX and Linux can all be parsed by the same code on the Xymon server. So the one client-side command to create [vmstat] in the client message will be universal across a wide range of OSes. If we can replace [vmstat] in this way, we may be able to do the same for [netstat] and [iostat] and a few others (by using sar with other options). We might also introduce an equivalent to [iostatdisk] and other things that don't yet exist in some OSes' client messages.</div><div><br></div><div>Adding support for a new OS (eg an exotic Linux-based NAS) becomes much easier if a "sar" package can be installed, or binaries for "sa" and "sar".can be copied onto the device.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
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 <br>
a very minimal install.<br>
<br>
<br>
<br>
On 9/19/19 7:53 PM, Jeremy Laidman wrote:<br>
> 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 <br>
> (assuming "ip addr show" gives similar output - probably doesn't, but you get the idea)?<br>
><br>
> 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, <br>
> perhaps even have a [sar] section of the client message, that is the first place that xymond goes when looking for statistics.<br>
><br>
> On Fri, 20 Sep 2019 at 00:52, Japheth Cleaver <<a href="mailto:cleaver@terabithia.org" target="_blank">cleaver@terabithia.org</a> <mailto:<a href="mailto:cleaver@terabithia.org" target="_blank">cleaver@terabithia.org</a>>> wrote:<br>
><br>
> On 9/18/2019 8:05 AM, Zdeněk Tlustý wrote:<br>
> > Hello,<br>
> ><br>
> > the script xymonclient-linux.sh is using commands like ifconfig,<br>
> > netstat, etc. These commands are marked as depreciated and some of the<br>
> > Linux distributions have removed them already. For example SuSE Linux<br>
> > Enterprise Server 15 has no support for netstat and ifconfig.<br>
> > The replacement are commands from iproute2 package like ip, ss,<br>
> > routel, etc.<br>
> > Are there any plan to replace depreciated commands with new ones?<br>
><br>
><br>
> Especially with SS and IP, it's something that's on the road map.<br>
> Unfortunately, doing that in a backwards-compatible way will still<br>
> keeping the 'linux' OStype/class 'linux' might prove difficult without a<br>
> lot more text processing. (This flag is split on the receiving side for<br>
> parsing out what client evaluations to run and how, since the output of<br>
> SunOS, Linux, BSDs, and other *nixes can vary widely.)<br>
><br>
> One could either move current OS's to something like "linux-old", or<br>
> have upgraded scripts under "linux-new", or do a lot of 'awk' calls in<br>
> xymonclient-linux.sh to try to duplicate previous output more precisely.<br>
> I'm not sure which is better there.<br>
><br>
> Regards,<br>
> -jc<br>
><br>
> _______________________________________________<br>
> Xymon mailing list<br>
> <a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a> <mailto:<a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a>><br>
> <a href="http://lists.xymon.com/mailman/listinfo/xymon" rel="noreferrer" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a><br>
><br>
><br>
> _______________________________________________<br>
> Xymon mailing list<br>
> <a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a><br>
> <a href="http://lists.xymon.com/mailman/listinfo/xymon" rel="noreferrer" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a><br>
<br>
<br>
_______________________________________________<br>
Xymon mailing list<br>
<a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a><br>
<a href="http://lists.xymon.com/mailman/listinfo/xymon" rel="noreferrer" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a><br>
</blockquote></div></div>