Now trigger a host or service notification for this host (custom notifications are fine to repro it, too). You should see the error from above.
To fix it, I just use Process check result to set the host state to UP for example and pass some output to the check result. Now, notifications work.
I think we need a check if $host.output$ is available before we refer to it and have a sane default or fallback.
Setup information:
icinga2 - The Icinga 2 network monitoring daemon (version: r2.10.2-1)
Copyright (c) 2012-2018 Icinga Development Team (https://icinga.com/)
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl2.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
System information:
Platform: Ubuntu
Platform version: 18.04.1 LTS (Bionic Beaver)
Kernel: Linux
Kernel version: 4.15.0-42-generic
Architecture: x86_64
Build information:
Compiler: GNU 7.3.0
Build host: 8baa592f9b22
Application information:
General paths:
Config directory: /etc/icinga2
Data directory: /var/lib/icinga2
Log directory: /var/log/icinga2
Cache directory: /var/cache/icinga2
Spool directory: /var/spool/icinga2
Run directory: /run/icinga2
Old paths (deprecated):
Installation root: /usr
Sysconf directory: /etc
Run directory (base): /run
Local state directory: /var
Internal paths:
Package data directory: /usr/share/icinga2
State path: /var/lib/icinga2/icinga2.state
Modified attributes path: /var/lib/icinga2/modified-attributes.conf
Objects path: /var/cache/icinga2/icinga2.debug
Vars path: /var/cache/icinga2/icinga2.vars
PID path: /run/icinga2/icinga2.pid
The slack-notitfications-command.conf fails with this error:
After some testing I found out that it's just related to "virtual" hosts without an icinga2 agent installed and found a repro:
Now trigger a host or service notification for this host (custom notifications are fine to repro it, too). You should see the error from above.
To fix it, I just use
Process check result
to set the host state to UP for example and pass some output to the check result. Now, notifications work.I think we need a check if $host.output$ is available before we refer to it and have a sane default or fallback.
Setup information: