Sehr geehrte Damen und Herren,
in der Zeit vom 24.12.2015 bis einschließlich 03.01.2016 befinde ich mich nicht
im Büro.
Beachten Sie bitte, dass Ihre EMail nicht automatisch weitergeleitet wird.
In dringenden Fällen wenden Sie sich bitte an unsere Hotline, 0203-378530, oder
an Herrn Hesselmann (hesselm...@opm-computer.de).
Wir wünschen Ihnen ein frohes Fest und einen guten Rutsch in das neue Jahr.
Mit freundlichen Grüßen
Ronny Bär
OPM EDV Service GmbH
Send icinga-users mailing list submissions to
icinga-users@lists.icinga.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.icinga.org/mailman/listinfo/icinga-users
or, via email, send a message with subject or body 'help' to
icinga-users-requ...@lists.icinga.org
You can reach the person managing the list at
icinga-users-ow...@lists.icinga.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of icinga-users digest..."
Today's Topics:
1. Re: Service acknowledgement (Assaf Flatto)
2. Re: Service acknowledgement (Markus Joosten)
3. Re: Service acknowledgement (Felix Cruz)
----------------------------------------------------------------------
Message: 1
Date: Thu, 24 Dec 2015 17:17:09 +0200
From: Assaf Flatto <ici...@flatto.net>
To: Icinga User's Corner <icinga-users@lists.icinga.org>
Subject: Re: [icinga-users] Service acknowledgement
Message-ID: <567c0c75.1020...@flatto.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Flix
Acknowledging an alert tell the system that you are working on resolving
and it till clear one the state has moved to the "OK" state.I have
encountered it in similar situation and learned it the hard way, but
that is the outcome.
So if you don't want to be alerted with a warning on such a low
threshold - change it to be more appropriate and not as easily dismissed.
Assaf
On 23/12/15 06:10, Felix Cruz wrote:
> Hi
>
> I have a basic question regarding expected behavior. Using Icinga version
> 1.13. I am with my company's monitoring team so not the administrator (with
> whom I will be discussing this as well ?).
>
> We check for available space on Linux partitions. I acknowledged the service
> check while in Warning status with the belief that if it moved from Warning
> to Critical (W=25%, C=12%), the acknowledgement would be removed and it would
> be in Critical unhandled. It in fact stayed in Acknowledged status even when
> it moved into Critical.
>
> Is this the expected behavior? Documentation leads me to believe otherwise
> (7.2 List of External Commands).
>
> Thanks for any help.
>
> Sent from my iPhone
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.icinga.org
> https://lists.icinga.org/mailman/listinfo/icinga-users
------------------------------
Message: 2
Date: Thu, 24 Dec 2015 18:46:27 +0100
From: Markus Joosten <markus.joos...@plumbe.de>
To: Icinga User's Corner <icinga-users@lists.icinga.org>
Subject: Re: [icinga-users] Service acknowledgement
Message-ID: <zarafa.567c2f73.03a5.3fa7bc4f3604e...@mail.plumbe.de>
Content-Type: text/plain; charset="utf-8"
Actually, this behaviour can be changed with the sticky bit of the
acknowledgement, which is enabled by default if I remember correctly.
When the sticky bit is removed, you should receive alerts for state changes
from warning to critical, even when you already acknowledged the warning.
Sent from my iPhone
On 24 Dec 2015, at 16:18, Assaf Flatto <ici...@flatto.net
<mailto:ici...@flatto.net> > wrote:
Flix
Acknowledging an alert tell the system that you are working on resolving
and it till clear one the state has moved to the "OK" state.I have
encountered it in similar situation and learned it the hard way, but
that is the outcome.
So if you don't want to be alerted with a warning on such a low
threshold - change it to be more appropriate and not as easily dismissed.
Assaf
On 23/12/15 06:10, Felix Cruz wrote:
> Hi
>
> I have a basic question regarding expected behavior.? Using Icinga version
> 1.13.? I am with my company's monitoring team so not the administrator (with
> whom I will be discussing this as well ).
>
> We check for available space on Linux partitions.? I acknowledged the service
> check while in Warning status with the belief that if it moved from Warning
> to Critical (W=25%, C=12%), the acknowledgement would be removed and it would
> be in Critical unhandled.? It in fact stayed in Acknowledged status even when
> it moved into Critical.
>
> Is this the expected behavior?? Documentation leads me to believe otherwise
> (7.2 List of External Commands).
>
> Thanks for any help.
>
> Sent from my iPhone
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org>
> https://lists.icinga.org/mailman/listinfo/icinga-users
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org <mailto:icinga-users@lists.icinga.org>
https://lists.icinga.org/mailman/listinfo/icinga-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.icinga.org/pipermail/icinga-users/attachments/20151224/7031081b/attachment-0001.html>
------------------------------
Message: 3
Date: Thu, 24 Dec 2015 15:15:04 -0500
From: Felix Cruz <felix1...@gmail.com>
To: Icinga User's Corner <icinga-users@lists.icinga.org>
Subject: Re: [icinga-users] Service acknowledgement
Message-ID: <09002737-5db6-4e3a-8709-7f4f33060...@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Hi All
Thanks for the info. We found that by default the acknowledgement is sticky.
Not a best practice OTS as the documentation leads one to believe that the
default behavior is NOT sticky.
Learning the hard way is an understatement as I work for a Cloud provider and
this could have been a disaster of disastrous proportions. Did I say
disaster??? We've set the default to not sticky and I removed all my acks.
Almost missed the ones that already moved into critical. We act on critical on
these so it was an attempt to clear unhandled warnings of these, as it is
essentially noise based on when we act.
I really think the default should be as the documentation says, which is that
it is removed on status change.
Thanks again.
Sent from my iPhone
> On Dec 24, 2015, at 12:46 PM, Markus Joosten <markus.joos...@plumbe.de> wrote:
>
> Actually, this behaviour can be changed with the sticky bit of the
> acknowledgement, which is enabled by default if I remember correctly.
>
> When the sticky bit is removed, you should receive alerts for state changes
> from warning to critical, even when you already acknowledged the warning.
>
> Sent from my iPhone
>
>> On 24 Dec 2015, at 16:18, Assaf Flatto <ici...@flatto.net> wrote:
>>
>> Flix
>>
>> Acknowledging an alert tell the system that you are working on resolving
>> and it till clear one the state has moved to the "OK" state.I have
>> encountered it in similar situation and learned it the hard way, but
>> that is the outcome.
>>
>> So if you don't want to be alerted with a warning on such a low
>> threshold - change it to be more appropriate and not as easily dismissed.
>>
>> Assaf
>>
>> On 23/12/15 06:10, Felix Cruz wrote:
>> > Hi
>> >
>> > I have a basic question regarding expected behavior. Using Icinga version
>> > 1.13. I am with my company's monitoring team so not the administrator
>> > (with whom I will be discussing this as well ).
>> >
>> > We check for available space on Linux partitions. I acknowledged the
>> > service check while in Warning status with the belief that if it moved
>> > from Warning to Critical (W=25%, C=12%), the acknowledgement would be
>> > removed and it would be in Critical unhandled. It in fact stayed in
>> > Acknowledged status even when it moved into Critical.
>> >
>> > Is this the expected behavior? Documentation leads me to believe
>> > otherwise (7.2 List of External Commands).
>> >
>> > Thanks for any help.
>> >
>> > Sent from my iPhone
>> > _______________________________________________
>> > icinga-users mailing list
>> > icinga-users@lists.icinga.org
>> > https://lists.icinga.org/mailman/listinfo/icinga-users
>>
>> _______________________________________________
>> icinga-users mailing list
>> icinga-users@lists.icinga.org
>> https://lists.icinga.org/mailman/listinfo/icinga-users
>>
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.icinga.org
> https://lists.icinga.org/mailman/listinfo/icinga-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.icinga.org/pipermail/icinga-users/attachments/20151224/ce126d00/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
------------------------------
End of icinga-users Digest, Vol 24, Issue 31
********************************************
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
