CHECK lines. Specifically, it is logging state and plugin-output data
as they existed BEFORE the passive service check is processed, instead
of representing data which is the actual incoming service-check result.
That is highly confusing. Here is an example of data logged for a service
which was set up to only accept passive checks. Note that for testing
purposes, passive checks have been set to be soft. Also note that for
testing purposes, active checks on the host were disabled.
Code: Select all
[1615235295] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;fakehost;icmp_ping_alive;0;initial OK result|
[1615235295] PASSIVE SERVICE CHECK: fakehost;icmp_ping_alive;0;(null)
[1615235356] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;fakehost;icmp_ping_alive;2;first critical result|
[1615235356] PASSIVE SERVICE CHECK: fakehost;icmp_ping_alive;0;initial OK result
[1615235356] SERVICE ALERT: fakehost;icmp_ping_alive;CRITICAL;SOFT;1;first critical result
[1615235486] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;fakehost;icmp_ping_alive;2;second CRITICAL result|
[1615235486] PASSIVE SERVICE CHECK: fakehost;icmp_ping_alive;2;first critical result
[1615235486] SERVICE ALERT: fakehost;icmp_ping_alive;CRITICAL;SOFT;2;second CRITICAL result
[1615235685] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;fakehost;icmp_ping_alive;2;Third Critical Result|
[1615235685] PASSIVE SERVICE CHECK: fakehost;icmp_ping_alive;2;second CRITICAL result
[1615235685] SERVICE ALERT: fakehost;icmp_ping_alive;CRITICAL;HARD;3;Third Critical Result