<div dir="ltr"><div dir="ltr"><div dir="ltr"><span style="font-size:12px"><span style="font-family:arial,helvetica,sans-serif"></span></span></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 26 Mar 2019 at 19:52, John Thurston <<a href="mailto:john.thurston@alaska.gov">john.thurston@alaska.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Does the procmem add-on not work just fine as is?<br>
Is it just the configuration-point which is annoying you?<br></blockquote><div> </div><div>Like I said, I haven't tried it, but it does something that I think should be part of Xymon - process memory monitoring - and the way it does it is not very 'xymonish' - the xymonish way to configure thresholds is in analysis.cfg, not in hosts.cfg.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> Another example is Xymondash:<br>
<br>
Oh please, no. Read my sig.<br>
<br>
If I wanted a json xml javascript monster, I'd select from the myriad of <br>
commercial products out there. We've run xymon/bb since the dawn of <br>
time. In the last twenty years, several other monster products have been <br>
brought in to "improve the look and feel" of our monitoring. All have <br>
died an early death, leaving our simple xymon server doing its duty and <br>
displaying its results.<br>
<br>
I'll stick with "boring that works".<br>
</blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
--<br>
Do things because you should, not just because you can.<br>
<br>
John Thurston 907-465-8591<br>
<a href="mailto:John.Thurston@alaska.gov" target="_blank">John.Thurston@alaska.gov</a><br>
Department of Administration<br>
State of Alaska<br></blockquote><div><br></div><div>Those were just 2 semi-random examples, another is probably calculation of CPU load thresholds based off the number of reported processors:</div><div><a href="https://wiki.xymonton.org/doku.php/monitors:cpu-load-calc">https://wiki.xymonton.org/doku.php/monitors:cpu-load-calc</a></div><div>Something _like_ this should be in Xymon, because otherwise the default CPU load thresholds are more or less meaningless and have to be configured for each server class / function intersection. But it should be in the core code, not a shell script that operates differently and independently of the core CPU calculation code.</div><div><br></div><div>For things that <40% users
don't want, they shouldn't be integrated - I'm with you on that John - and what I suggested about Xymondash being more like a suggested optional package is maybe a middle-ground. But if the core function is something >40% users would want, then the feature should be integrated, because it lowers the barriers to entry for users and adds to the core feature list / reduces the core annoyance list. I've not tried any of these 3 add-ons because they are add-ons, and because the desire for them is relatively recent or intermittent, but I would have implemented them if they were part of the core package. (I've tried other add-ons of course, and created a few of my own over the years.)<br></div><div>
<br clear="all"><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><span><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">
<div style="text-align:left"><span style="font-size:12px"><span style="font-family:arial,helvetica,sans-serif">Kind regards,<br><br>SebA</span></span></div></div></div></div></div></div></div></span></div></div></div>
</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On 3/26/2019 10:49 AM, SebA wrote:<br>
> I think merging some add-ons into the Xymon source code should be <br>
> considered where those add-ons would be widely used, subject to <br>
> licensing restrictions.<br>
> <br>
> For example, and I have not yet tested this add-on, but a way to alert <br>
> on processes using too much memory looks increasingly useful to me <br>
> (together with graphing of memory for certain processes):<br>
> <a href="http://tools.rebel-it.com.au/xymon-procmem/" rel="noreferrer" target="_blank">http://tools.rebel-it.com.au/xymon-procmem/</a> <br>
<br>
> Ideally the shell code that add-on uses would be converted to support in <br>
> the C code so that this could be configured in analysis.cfg rather than <br>
> hosts.cfg though.<br>
> <br>
> Another example is Xymondash:<br>
> <a href="https://github.com/daduke/Xymondash" rel="noreferrer" target="_blank">https://github.com/daduke/Xymondash</a> <br>
<br>
> I haven't used it yet either, but it sounds good. Having said that, <br>
> development on that shouldn't be stymied by locking it to Xymon releases <br>
> - and it requires Python >= 3.5 (or 3.4). Maybe as a post-installation <br>
> task Xymon could ask if you wish to install it, check dependencies, ask <br>
> a few questions, download and install it?<br>
> It would be good to be able to present a more modern GUI as part of Xymon.<br>
> <br>
> Kind regards,<br>
> <br>
> SebA<br>
> <br>
<br>
</blockquote></div></div></div>