[collectd] Notification flood

Darren Worrall dw at darrenworrall.co.uk
Wed Mar 2 11:41:32 CET 2011

Hi Sebastian,

We haven't actually set any threshold configuration on the server,
preferring to let the client decide what threshold values are
reasonable (or even disable them completely), so Persist defaults to
False according to the docs. The client configuration is very simple
(we're testing load thresholds):

  <Type "load">
    WarningMax 1
    FailureMax 2

The client is 4.8.2, and the server is 4.10.1.



On 2 March 2011 10:35, Sebastian Harl <sh at tokkee.org> wrote:
> Hi Darren,
> On Wed, Mar 02, 2011 at 10:30:08AM +0000, Darren Worrall wrote:
>> Just using the logfile plugin to handle notifications for now, we're
>> seeing that on the node where a threshold is breached, we get 1
>> notification logged as per the documentation. However, that node is
>> configured to send its data to a 'server' over the network, and on
>> that host, the same notification is _constantly_ written to its log
>> file, over and over again, and future notifications are ignored (or at
>> least appear to be). Any suggestions where I'm going wrong?
> What does your configuration look like on the server and on the client?
> Have you set "Persist" to "false" on the server? See the
> collectd.conf(5) manpage for defaults.
> HTH,
> Sebastian
> --
> Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/
> Those who would give up Essential Liberty to purchase a little Temporary
> Safety, deserve neither Liberty nor Safety.         -- Benjamin Franklin
> Version: GnuPG v1.4.9 (GNU/Linux)
> 3jQAnj9AnB7sFAENN+nS9cJWYtwtqwOZ
> =Jcjt

More information about the collectd mailing list