Thanks
Found it , i was under impression that user group will cover the contact
mails?
* end = 10800
* type = "Notification"
* types = [ "Acknowledgement", "Custom", "DowntimeEnd",
"DowntimeRemoved", "DowntimeStart", "FlappingEnd", "FlappingStart",
"Problem", "Recovery" ]
% = modifi
If the UserGroup has no members, you won’t get any notifications.
Kind regards,
Michael
> On 10 Feb 2017, at 09:40, Tal Bar-Or wrote:
>
> Thanks
> Found it , i was under impression that user group will cover the contact
> mails?
>
>
>
>
> * end = 10800
> * type = "Notification"
>
There is members and yet no was triggered , so added users directly to the
mail object , waiting for the resaults
Thanks
On Fri, Feb 10, 2017 at 8:45 AM, Michael Friedrich <
michael.friedr...@icinga.com> wrote:
> If the UserGroup has no members, you won’t get any notifications.
>
> Kind regards,
> On 10 Feb 2017, at 10:10, Tal Bar-Or wrote:
>
> There is members and yet no was triggered , so added users directly to the
> mail object , waiting for the resaults
https://docs.icinga.com/icinga2/latest/doc/module/icinga2/toc#!/icinga2/latest/doc/module/icinga2/chapter/troubleshooting#notifi
Hello
If we have a host H with a service S, when icinga detects H is down it
marks it as SOFT state and doesnt send any notification until it reaches
max_check attempts.
So far everything is good.
The problem we have is even if S has max_check_attempts 3, icinga marks it
HARD state as soon as it
On Friday 10 Feb 2017 at 13:16, Jorge Ferrando wrote:
> Is there anyway to configure icinga to not send notifications for services
> if the host is DOWN?
>
> and
>
> Is there anyway to configure icinga to not send notifications for services
> if the host is DOWN but in SOFT state?
See 3.9 of
h
Hi Antony
I already read that before but I don't see how that can solve my problem.
Can you clarify it?
I also read in icinga (not icinga2) documentation this:
"Hard states occur for hosts and services in the following situations:
-
When a service check results in a non-OK state and its
On Friday 10 Feb 2017 at 13:29, Jorge Ferrando wrote:
> Hi Antony
>
> I already read that before but I don't see how that can solve my problem.
> Can you clarify it?
"If the dependency should be triggered in the parent object's soft state, you
need to set ignore_soft_states to false."
Have you
I've had this issue posted to this mailing list some months ago, and the
reply I received was that the dependencies that a service has to it's
parent host are automatically created.
So, what definitions would anybody need to create ?
I am also interested in fixing this.
On 2/10/2017 3:44 PM,
On Friday 10 Feb 2017 at 15:54, Horatiu N wrote:
> I've had this issue posted to this mailing list some months ago, and the
> reply I received was that the dependencies that a service has to it's
> parent host are automatically created.
>
> So, what definitions would anybody need to create ?
Wel
>
> Maybe you should show us the dependency definitions you've created for an
> example host/service, so we can see where you're starting from.
>
>
>From icinga2 documentation:
"A service can depend on a host, and vice versa. A service has an implicit
dependency (parent) to its host."
Why should
On Friday 10 Feb 2017 at 16:58, Jorge Ferrando wrote:
> > Maybe you should show us the dependency definitions you've created for an
> > example host/service, so we can see where you're starting from.
> >
> >From icinga2 documentation:
> "A service can depend on a host, and vice versa. A service ha
Hi,
We have build an Icinga2 Operator for Kubernetes. https://github.
com/appscode/searchlight
This will automatically apply an alert set on Kubernetes RC, Deployment,
etc to individual pods. Please give it a try! Let us know in Github if you
have feedback,
Thanks.
___
I'll try it on Monday and let you know.
Thanks!
On Fri, Feb 10, 2017 at 6:02 PM, Antony Stone <
antony.st...@icinga.open.source.it> wrote:
> On Friday 10 Feb 2017 at 16:58, Jorge Ferrando wrote:
>
> > > Maybe you should show us the dependency definitions you've created for
> an
> > > example hos
14 matches
Mail list logo