Posts by r2kevin

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

    So obvious... Thanks you very much :)

    1. curl -k -s -u 'root:icinga' \
    2. -H 'Accept: application/json' \
    3. -X POST 'https://localhost:5665/v1/objects/hosts?' \
    4. -d '{ "attrs": { "enable_active_checks": false } }' \
    5. | python -m json.tool

    Is it possible to do this for host and its services in only one call? I tried with "joins" but I got a "No objects found." error.


    I checked the API documentation, but I didn't found any "action" to disable active checks from host or service.

    Ok I can use schedule-downtime to block notification, and right now this is what I do. But I really need to disable checks 'cause my checks come with a 120s timeout.

    For the story, every month, I reboot ~2000 hosts. Let's say ~6000 services in timeout from my satellite zone. It will kill them no?^^

    How do you disable check for a host and its services? Without reload.

    Thanks for your help.


    I saw the "Check execution" section, but as you said I would like to see the entire command with all attributes.

    EDIT: I ask this because I'm a Thruk user since really long time ^^ And this "check command" section is a little bit useful :)

    Hey Icinga Community :)

    Is anyway to display the check command directly from the service tab? As far as I know, the only way to show it is to click on "Inspect" link.

    I'm just looking for a short way :thumbsup:

    Thanks guys.


    I saw that Director documentation strongly suggest to don't use conf.d and Director in the same time. But I was not sure about API :/

    So thanks you for the confirmation!

    I'll try to adapt the existing perl library for the Director and share it with the community. Even if I'm not a Perl expert ^^

    Hey the community!

    TL;DR: Should I enable accept_config and accept_command parameters on all servers? Even on the Director server?

    I'm reading you since a long time as an anonymous user but today I would share with you a problem about api and director.

    Here is my configuration:

    - 1 master with Director (Enabled features: api command ido-mysql livestatus mainlog notification)

    - 1 master (Enabled features: api command ido-mysql livestatus mainlog notification)

    - 1 satellite (Enabled features: api checker mainlog)

    - 1 satellite (Enabled features: api checker mainlog)

    All "API" feature are configured with "accept_config = true" and "accept_command = true" except on the master with Director module.

    I'm getting this warning message from the master server with Director:


    [2017-11-27 18:23:03 +0100] warning/ApiListener: Ignoring config update. 'api' does not accept config.

    My question: Should I enable the accept_config and accept_command parameter on the master server where Director is installed?

    If more details are needed, let me know.

    Thanks in advance for your help.