Alignak-monitoring / alignak

Monitoring tool, highly flexible and new standard oriented
https://alignak-monitoring.github.io
GNU Affero General Public License v3.0
86 stars 19 forks source link

External commands do not propagate through realms #708

Open mohierf opened 7 years ago

mohierf commented 7 years ago

On the demo configuration (realms North and South, children of default realm All), with 2 receivers (All and North), the external commands do not propagate, except for the realm All hosts. the ws module is attached to the receiver in the realm All.

:+1: - external command for an host in the realm All:

==> /usr/local/var/log/alignak/receiverd.log <==
[2017-01-24 05:40:39 CET] WARNING: [alignak.external_command] Missing timestamp in command 'PROCESS_HOST_CHECK_RESULT', using [1485232839] as a timestamp.

==> /usr/local/var/log/alignak/schedulerd.log <==
[2017-01-24 05:40:39 CET] WARNING: [alignak.external_command] Missing timestamp in command 'PROCESS_HOST_CHECK_RESULT', using [1485232839] as a timestamp.

==> /usr/local/var/log/alignak/monitoring-logs.log <==
[1485232839] INFO: PASSIVE HOST CHECK: always_down;0;Tests Fred
[1485232839] INFO: EXTERNAL COMMAND: PROCESS_HOST_CHECK_RESULT;always_down;0;Tests Fred

The command is sent to the scheduler and executed

:-1: - external command for an host in the realm North:

==> /usr/local/var/log/alignak/receiverd.log <==
[2017-01-24 05:43:06 CET] WARNING: [alignak.external_command] Missing timestamp in command 'PROCESS_HOST_CHECK_RESULT', using [1485232986] as a timestamp.

==> /usr/local/var/log/alignak/schedulerd-north.log <==
[2017-01-24 05:43:06 CET] WARNING: [alignak.external_command] Missing timestamp in command 'PROCESS_HOST_CHECK_RESULT', using [1485232986] as a timestamp.

The command is sent to the linked scheduler, but that's all ... host not found?

:-1: - external command for an host in the realm South:

==> /usr/local/var/log/alignak/receiverd.log <==
[2017-01-24 05:43:32 CET] WARNING: [alignak.external_command] Missing timestamp in command 'PROCESS_HOST_CHECK_RESULT', using [1485233012] as a timestamp.

The command is not even sent to the scheduler...


Indeed, it seems there are two problems:

mohierf commented 7 years ago

A current workaround is to use a receiver with the sub realm management parameter

mohierf commented 6 years ago

To be checked with the newcoming 1.1 version