Thanks for the input guys
assign where host.name in [ “h1”, “h2" ]
assigning it this way looks clean and yeah its gonna be expensive.
Will go ahead with this approach and try to keep the usage of the above to
the minimum.
At the moment this feels like the best available approach. WIll ping back
i
> On 21. Dec 2017, at 09:02, Joosten, Markus wrote:
>
> Am 2017-12-21 04:20, schrieb Jayapandian Ponraj:
>> Thanks for the reply
>> We do heavily use apply rules based on host variables and for hostgroup
>> definitions, but once in a while we come across a service which is spread
>> across 2
Am 2017-12-21 04:20, schrieb Jayapandian Ponraj:
Thanks for the reply
We do heavily use apply rules based on host variables and for hostgroup
definitions, but once in a while we come across a service which is
spread across 2 or 3 hosts which don't share anything in common. We can
go ahead add
On 20-Dec-2017 8:55 PM, "Michael Friedrich"
wrote:
> On 20. Dec 2017, at 15:57, Jayapandian Ponraj
wrote:
>
> Is it possible to assing an array of host objects to a service object ?
>
> In icinga1 we could add multiple hosts separated by commas. Is it still
possible in icinga2? If not are ther
> On 20. Dec 2017, at 15:57, Jayapandian Ponraj wrote:
>
> Is it possible to assing an array of host objects to a service object ?
>
> In icinga1 we could add multiple hosts separated by commas. Is it still
> possible in icinga2? If not are there any alternatives ?
Look into the rich possib
Is it possible to assing an array of host objects to a service object ?
In icinga1 we could add multiple hosts separated by commas. Is it still
possible in icinga2? If not are there any alternatives ?
Icinga1 Doc:
host_name:
This directive is used to specify the short name(s) of the host(
