Service alerts misinterpreted

Jason Martin jhmartin at toger.us
Tue Jul 5 05:33:34 CEST 2005


On Mon, Jul 04, 2005 at 04:05:23PM +0100, Ian Davidson wrote:
> The 3x service alerts which are nsca'd to the central server are:
> 
> SERVICE ALERT: emea-cns3;check-halo-service;CRITICAL;SOFT;1; Halo: Stopped
> SERVICE ALERT: emea-cns3;check-halo-service;CRITICAL;SOFT;2; Halo: Stopped
> SERVICE ALERT: emea-cns3;check-halo-service;CRITICAL;HARD;3; Halo: Stopped
> 
> 
> But in the nagios.log file, these are interpreted as:
> 
> EXTERNAL COMMAND: 
> PROCESS_SERVICE_CHECK_RESULT;emea-cns3;check-halo-service;2; Halo: Stopped
> EXTERNAL COMMAND: 
> PROCESS_SERVICE_CHECK_RESULT;emea-cns3;check-halo-service;2; Halo: Stopped
> EXTERNAL COMMAND: 
> PROCESS_SERVICE_CHECK_RESULT;emea-cns3;check-halo-service;2; Halo: Stopped
Looks right to me. What is wrong with this? External commands
are how NSCA communicates to Nagios. The concept of hard and
soft is something the central server has to decide for itself.
'2' in the externla command means CRITICAL.

-Jason Martin
-- 
Useless Invention: Ejector seats for helicopters.
This message is PGP/MIME signed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 211 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20050704/34e3c83b/attachment.sig>


More information about the Users mailing list