On Tue, 26 Mar 2019 at 23:15, Bruce Ferrell <user-24fbf1912cfe@xymon.invalid> wrote:
On 3/26/19 11:49 AM, SebA wrote:
I think merging some add-ons into the Xymon source code should be
considered where those add-ons would be widely used, subject to licensing
restrictions.
For example, and I have not yet tested this add-on, but a way to alert
on processes using too much memory looks increasingly useful to me
(together with graphing of memory for
certain processes):
http://tools.rebel-it.com.au/xymon-procmem/
Ideally the shell code that add-on uses would be converted to support in
the C code so that this could be configured in analysis.cfg rather than
hosts.cfg though.
Another example is Xymondash:
https://github.com/daduke/Xymondash
I haven't used it yet either, but it sounds good. Having said that,
development on that shouldn't be stymied by locking it to Xymon releases -
and it requires Python >= 3.5 (or
3.4). Maybe as a post-installation task Xymon could ask if you wish to
install it, check dependencies, ask a few questions, download and install
it?
It would be good to be able to present a more modern GUI as part of
Xymon.
Kind regards,
SebA
If you've not tested the functionality, why on earth would you think it
should be merged? *just* because it's JS/JSON?
I didn't say it should be merged. I was just giving a few examples of
add-ons that cover functionality that should be considered for merging /
adding to the Xymon core package. Maybe the subject of the thread and
initial wording was misleading, and I apologize for that.
The procmem tool is somewhat interesting but if you KNOW have a process
that needs to be monitored for it's memory use, don't you think that an
indication of an issue with that
process that needs fixing? Ya know, memory leaks ARE kind of considered
very to be bad form, or maybe that's just me.
Well, maybe we could just monitor the memory usage of all processes on the
same rrd chart - that way it shouldn't get too big - is that correct?
That said, I do a "kill -9" on devmon and restart it via cron because I
know it balloons on my system; I know it because xymon told me something
was using up memory. Once I did
the diagnosis of what and how often, my remedial action was to just kill
it off and restart it. Inelegant perhaps, but I seem to be the only one
experiencing this particular
issue. Why would I do monitoring on it rather than fixing the issue if
not the process? Seems like asking how many angels can I get to dance on
the head of a pin and when exactly
do they start falling off.
How did you do the diagnosis of how often it would need restarting?
Process memory monitoring is what you need to determine how bad the memory
leak is and how often something would need restarting. Maybe you ran ps
via cron and put that into a log file and then analysed that - but it's
easier to look at a chart.
Kind regards,
SebA