[martialblog]

Fixes #42

[martialblog]

Hi @UiP9AV6Y

This PR should enable the described use-case. Feel free to test it and give me feedback.

Thanks

[UiP9AV6Y]

the change looks good overall, just minor nitpicks

[UiP9AV6Y]

i did run into an issue while testing the feature against the local docker-compose stack.

the bridge sent the following request

{
  "exit_status": 2,
  "plugin_output": "Host down",
  "ttl": 0,
  "filter": "host.name==\"gaff.bac.test\"",
  "type": "Host"
}

and received the following response from the Icinga2 API

{
  "results": [
    {
      "code": 400,
      "status": "Invalid 'exit_status' for Host gaff.bac.test."
    }
  ]
}

not sure if my setup is broken or something else is not working as intended. the error is currently not logged; i have opened #46 as a result

[martialblog]

@UiP9AV6Y Thanks for the review. You're setup isn't broken it's the exit status mapping for host checks.

[UiP9AV6Y]

can confirm. host objets are now updates based on alerts.

i have refactored the docker-compose setup to include an example for a host-check-based alert in a feature branch

feel free to cherry pick the commit, otherwise i can make a follow-up PR

[martialblog]

Thanks for the feedback. I think this will be the last change for the version v1.1.0.