Posts by swizzly

This forum was archived to /woltlab and is now in read-only mode.

    Hi

    I would like to sync downtimes in Icinga Director with a sync rule, but I cant find any downtime relevant destination fields.

    Can I reach the downtime attribute as a custom variable, or is it not possible?

    Cheers

    Hi

    Is it possible to let the user roles synchronised among the nodes of a distributed monitoring Environment?

    I have several icinga2 servers in a distributed HA config, the hosts, services, checks, downtimes etc. are all synchronised among the nodes, but the user roles are not. Is it possible to let them sync?

    Can I use director for this purpose?

    Cheers

    Hi

    Is it possible to find out on which icinga2 node is Director module running in a distributed monitoring Environment using Icinga2 API?

    I have several nodes in my master zone and one of them runs Director to generate and distribute the configs for all the nodes. I would like to find out from an external script, that makes Icinga2 API calls, which node runs Director.

    I know, that I could make MySQL queries or SSH connections to each node, and check whether the DB for the Director is there or if there are config files for Director, but I would prefer icinga2 API calls.

    Is it possible?

    Cheers

    I set up an distributed icinga2 monitoring environment with two master servers with individual MySQL DBs.

    The setup seems to work, the checks are distributed between the two nodes.

    I noticed if a new downtime gets created through the GUI of the first master server, it gets synchronised to the second server, but if the downtime gets deleted on the second server it won't be removed from the first server. The same happens if the downtime gets created on the second server, it won't be created on the first server.

    So it seem, that the second server can not change the config on the first server. How can I make it work?

    When I create my host object in Director I would like to assign a recurring maintenance periods/downtimes from my central datasource for the given host (and all of its services).

    Is it possible to schedule recurring downtimes for host and service objects in icinga2 director?

    I haven't found any options in the current icinga2 Director release (v.1.4.2).

    Hi

    I have a running Icinga2 Satellite setup with a master and a satellite zone, both with a single endpoint. I have several hosts in both zones with many services. Currently everything works fine, the hosts in the satellite zone are monitored through the endpoint in the satellite zone, the inhabitants of the master zone are monitored through the master endpoint. In the close future though I need to monitor some services on my hosts in the satellite zones from the master endpoint and not from the satellite.

    In Icinga2 Director I tried several combinations of the options "Run on Agent" and "Cluster zone" inthe service template in question. Unfortunately, they either result in a faulty config, that Director complains about non-existing Endpoints (it expects an endpoint for each host) or it renders the configs, but the Services are still monitored from the satellite endpoint and not from the master.

    Does someone have an idea how to make it right?

    Hi


    I use LDAP as my datasource and I would like to import Timeperiods to Icinga. In the LDAP I have the Timeperiod data in iCAL format. I managed to make "Import source" with several property modifiers that build a new property that at the end looks like this:

    "monday = 00:00 - 24:00"

    The problem I can't forge a sync rule that would result in something like this:

    Code
    1. object TimePeriod "test" {
    2. import "legacy-timeperiod"
    3. ranges = {
    4. "monday" = "00:00-24:00"
    5. }
    6. }

    What I get is like:

    Code
    1. object TimePeriod "test" {
    2. import "legacy-timeperiod"
    3. ranges = {
    4. "0" = "monday = 00:00 - 24:00"
    5. }
    6. }

    Has anyone managed to write a sync rule that works as expected?

    Hi

    I have the same Problem. Only, I use LDAP as my datasource. I can write "Import source" that builds an attribute that looks like this:


    "monday = 00:00 - 24:00"


    But I can't forge a sync rule that would result in something like this:


    Code
    1. object TimePeriod "test" {
    2. import "legacy-timeperiod"
    3. ranges = {
    4. "monday" = "00:00-24:00"
    5. }
    6. }

    What I get is like:


    Code
    1. object TimePeriod "test" {
    2. import "legacy-timeperiod"
    3. ranges = {
    4. "0" = "monday = 00:00 - 24:00"
    5. }
    6. }

    Has anyone managed to write a sync rule that works as expected?

    I adapted my script to schedule/remove downtimes for all services on every host in downtime. The problem, I haven't found a way to batch create and remove multiple downtimes in a single API request, is it possible? I have to create and remove every single downtime (host & service) schedule in a loop, and it takes a lot more time than if I would have to deal only with host downtimes (30s vs. 4s).

    Is there a way to create and remove multiple downtimes in a single API call?

    Hi Michi,

    Thanks for the answer. I thought it would be simpler to solve the problem through dependencies, as the removal of downtimes also needs to happen automatically (external script). In this case the script has to handle a large number of service downtimes vs. a few host-downtimes.

    I can modify the script to schedule/remove downtimes for the hosts and all the belonging services.

    Is it what you meant in your last sentence?

    Hi,

    Since the newest release Icinga Director supports "dependencies" (though it says this feature is still experimental).

    Currently, the feature is not yet documented, or at least I haven't found anything in the docu.

    Does anyone know how to implement the following config: Director creates automatically host objects based on data in LDAP. The Downtime of host objects is also scheduled automatically based on LDAP Attributes (it is not done by Director, but it is done by an external script). The checking of services belonging to host objects in downtime should be disabled/paused as long as the host downtime is defined.

    I am Aware of that Icinga2 stops alarming of services belonging to a host that is "down" but it is different, as I need to disable checking and alarming for hosts that might be "up", but have a downtime scheduled.

    Does anyone have an idea how to solve this?

    Hi

    Very cool, but how can I use the icons? I have them installed, I can see them under the URL mentioned above. I tried to copy the codes next to the text, but it didn't work, it printed only the code instead of the icon on the screen.

    so for example: