On Monday 24 October 2016 at 22:37:22, Gerald Vogt wrote:
> On 24/10/2016 22:05, Antony Stone wrote:
> >
> > So, I'm trying to work out where the 10% and 20% default thresholds are
> > defined.
>
> Well, I would run this:
>
> # icinga2 object list -t CheckCommand -n disk
>
> which would tell y
Hi.
Is it possible to get Icinga to alert in either of the following situations:
1. The check value is lower than the previous check value.
I'm looking for a way to monitor something which is assumed to steadily
increase (maybe stay the same between checks, but not go down) and I want an
alert
On Wed, Oct 26, 2016 at 11:29 PM, Markus Frosch
wrote:
>
> Uhm, it would be interesting to know what you are trying to achieve.
All of my hosts have a variable vars.range = "". cluster is
the name we give to a group of identical hosts. This name is assigned
in our range repository outside Icinga
I just had another thought. In one of my hosts.conf files, I already
have an array which contains the names of all the clusters. If I could
access this array from other .conf files, then I can iterate through
each cluster, creating the Service objects that I need. Is it possible
to make the value o
Hi Gerald,
Thanks for the fast response, I guess I misunderstood the service
definition.
I thought of the values in there as defaults that could be overwritten
by a redefinition at the host level.
I redefined the service leaving the default values empty and setting
them in the host definition
I put together a workaround that I am not entirely satisfied with. It
leaves a lot to be desired.
I modified my config generation outside icinga to create a file with a
"const" variable "const all_clusters", an array containing all the
cluster names. I have icinga2.conf including this file, so tha
