Check services with NC_NET with nsca
Andreas Ericsson
ae at op5.se
Wed Feb 9 11:00:45 CET 2005
Pedro A. Damaso wrote:
> I'm trying to recover information from windows machines out of my
> network. They are behind a router because of that I'm planning to use
> the passive checks from NC_Net. Rigth now I'm trying to configure one
> host but I'm lost about the sintax of service check that I must use in
> my nagios server.
>
> For this moment this is my configuration:
>
> Windows Machine:
>
> passive.cfg ----
>
> 1 clientversion
> 2 cputotal -l 10,80,90,5,20,90
> 3 uptime
>
> Nagios Server:
>
> -------------
> | hosts.cfg |
> -------------
>
> define host {
> name windows-nsca ; nombre de la clase de
> la que deben heredar todos los chequeos pasivos
> notifications_enabled 1 ; Host notifications are enabled
> check_command ; asi esta bien
> max_check_attempts 1 ; como no hacemos check-command,
> esto tloco
> event_handler_enabled 0 ; Host event handler is disabled
> flap_detection_enabled 1 ; Flap detection is disabled
> 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
> register 0 ; DONT REGISTER THIS DEFINITION -
> ITS NOT A REAL HOST, JUST A TEMPLATE!
> passive 1 ; Tipo de Chequeo
> }
>
> define host {
> use windows-nsca
> host_name XP_Ofi
> alias Xp de la Ofi
> address 192.168.1.203
> notification_interval 120
> notification_period 24x7
> notification_options d,u,r
> register 1;
> }
>
> ----------------
> | services.cfg |
> ----------------
>
> define service {
> name windows-service-nsca ; The 'name' of
> this service template, referenced in other service definitions
> active_checks_enabled 0 ; Active service checks are
> disabled
> is_volatile 0 ; no es un servicio volatil
> 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 1 ; Service notifications are
> enabled
> event_handler_enabled 1 ; Service event handler is
> enabled
> flap_detection_enabled 1 ; Flap detection 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
> register 0 ; DONT REGISTER THIS DEFINITION
> - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
> }
>
> define service {
> host_name XP_Ofi
> service_description XP monitorized with NC_Net with passive
> support
> check_period 24x7
> max_check_attempts 3
> normal_check_interval 5
> retry_check_interval 1
> contact_groups admins
> notification_interval 120
> notification_period 24x7
> notification_options w,u,c,r
> check_command ?????????????????????
> }
>
>
> Thanks
>
Was there a question in here or were you just telling us of your plans?
If you're referring to the thousand and one question marks at
check_command, set it to something that returns critical upon invocation
but set the check_period (or some such) to none. Then read up on
freshness checking and implement away til your heart's content.
--
Andreas Ericsson andreas.ericsson at op5.se
OP5 AB www.op5.se
Lead Developer
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list