how to create a no-alert-status-service check template ?

[nagmoto]

Hi,
On a centos 6.6/Nagios 3.5.1, I am trying to create a special service check template that can be used for creating a service check called "noalertstatus-service".
With following definition, I can now not receive email alerts, but the critical/warning status still showing when threshold condition met.

Please advise

Code: Select all

from /etc/nagios/object/template.cfg
<snipped>
define service{
   name                            noalertstatus-service ; Just check, no alerting, no status of critical,warning...
   use                              srv-pnp              ; pnp4nagios trending
   active_checks_enabled           1            ; Active service checks are enabled
   passive_checks_enabled          1            ; Passive service checks are enabled/accepted
   parallelize_check               1            ; Active service checks should be parallelized
                                                ; (disabling this can lead to major performance problems)
   obsess_over_service             1            ; We should obsess over this service (if necessary)
   check_freshness                 0            ; Default is to NOT check service 'freshness'
   notifications_enabled           0            ; Service notifications are disenabled
   event_handler_enabled           1            ; Service event handler is enabled
   flap_detection_enabled          1            ; Flap detection is enabled
   failure_prediction_enabled      1            ; Failure prediction is enabled
   process_perf_data               1            ; Process performance data
   retain_status_information       1            ; Retain status information across program restarts
   retain_nonstatus_information    1            ; Retain non-status information across program restarts
   is_volatile                     0            ; The service is not volatile
   check_period                    24x7         ; The service can be checked at any time of the day
   max_check_attempts              3            ; Re-check the service up to 3 times in order to determine its final (hard) state
   normal_check_interval           10           ; Check the service every 10 minutes under normal conditions
   retry_check_interval            2            ; Re-check the service every two minutes until a hard state can be determined
   contact_groups                  admins       ; Notifications get sent out to everyone in the 'admins' group
   notification_options         n       ; Send notifications about warning, unknown, critical, and recovery events, n for null
   notification_interval           60           ; Re-notify about service problems every hour
   notification_period             24x7         ; Notifications can be sent out at any time
   register                        1            ;
  }

<snipped>

[Box293]

but the critical/warning status still showing when threshold condition met.

You are not going to be able to avoid that. If a threshold condition is met then it will then be at that state (warning/critical/unknown). All you've done is stop notifications from being sent.

I you don't want a critical/warning status then change the thresholds to a level where they won't be triggered.

[nagmoto]

Box293, thanks for the reply.
My workaround will be to define commands in commands.cfg with max threshold for each type of checks, then the high threshold wont be reached by any system.

[cmerchant]

Ok. We'll go ahead and close this thread. Thanks.