<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<p>Den 22.11.2013 03:00, Jeremy Laidman skrev:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 22 November 2013 08:49, Mark Felder <span><<a href="mailto:feld@feld.me">feld@feld.me</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: #cccccc; border-left-style: solid; padding-left: 1ex;">
<div class="im"> </div>
<a href="http://imgur.com/a/P4Qq1">http://imgur.com/a/P4Qq1</a></blockquote>
<div> </div>
<div>Now, that's what I want!</div>
</div>
</div>
</div>
</blockquote>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>[... snip ...]</div>
</div>
</div>
</div>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">
<div dir="ltr">
<div class="gmail_extra">
<div>A bigger problem is that Xymon's genericised way of reporting memory is a call to unix_memory_report() with parameters for total, used and actual - and that's all. (For FreeBSD and others, "actual" is set to -1.) The function unix_memory_report() does the memory threshold checks (via status message) and also governs what gets sent to the RRD files. If I wanted to alert on all available memory numbers, and to have them all on the graph for the "memory" page, I'd have to find another way to get them sent to the RRD files and to check for threshold violations, because Xymon is simply not geared up to do this. And it probably won't ever be, because different OSes do memory management differently.</div>
</div>
</div>
</blockquote>
<p><rant>Memory reporting is probably *the* single most bothersome monitoring item in Xymon. Every single OS seems to count memory differently, and different sources claim different ways of interpreting the same data. Not to mention that the OS providers frequently change what the numbers mean, or come up with new ways of reporting them. </rant></p>
<p>The way Xymon reports memory handling is very much due to historical events - how it was done in Big Brother. I agree that the "one-size-fits-all" approach in the current code is not the best way of doing it, unless your OS happens to nicely fit into the real+actual+swap metrics mold.</p>
<p>However, it doesn't have to be that way.</p>
<p>The clientdata handling code is specific for each type of client, and it would be perfectly possible for that code to NOT use the "unix_memory_report()" routine. The client code just needs to generate a status message; it can do that without calling unix_memory_report(). But you need to write some code specifically for that type of client, including the bit that grabs configuration data from analysis.cfg.</p>
<p>You can also send data into an RRD file with a different layout, so you can have more data. Getting that rrd-graph to show up on a "memory" status is the tricky part, and right now I would recommend that you simply use a different name for the memory status.</p>
<p> </p>
<p>So it is not an un-solvable problem, but someone needs to figure out just how the memory metrics can be found by the client code, and how it should be interpreted over on the Xymon server.</p>
<p> </p>
<p>Regards,</p>
<p>Henrik</p>
<p> </p>
<div> </div>
</body></html>