Check for memory leaks

[Marcel]

Hi Andrew,

On Thu, Nov 19, 2009 at 4:11 PM, Kaplan, Andrew H. <AHKAPLAN at partners.org>wrote:

> I do have the pnp4-nagios utility installed on the Nagios server.
> Among the trends that are graphed by it is Current Load.
>
If Current Load is the trend to look at, which of the three data sources
> associated with it,
> load1 load5 load15, would be the one affiliated with memory?
>

Load means the number of processes per processor waiting in the scheduler's
RUN QUEUE. The load1 is the average of that number in the last minute, load5
it's the same average within 5 minutes, and load15 the same for the last 15
minutes. It does NOT relates to memory leak detection.

On Thu, Nov 19, 2009 at 3:48 PM, Kaplan, Andrew H. <AHKAPLAN at partners.org>wrote:
>
>>  There are indications that an application on the monitored system is
>> causing a slow memory leak.
>> Is there a plugin or histogram setting that is available that would help
>> check for memory leaks on
>> the remote system? Thanks.
>>
> Trending is more suitable for graphing solutions that uses RRDs.
> Nagios is more likely to be used as an exception monitoring tool, though it
> might be used to generate graphs as well.
>

Cheers,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20091119/a37f6836/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null