Results 1 to 3 of 3

Thread: Passive service checks / check_period / notification_period conflict !

  1. #1
    Member
    Join Date
    May 2013
    Location
    France - Valence
    Posts
    91

    Passive service checks / check_period / notification_period conflict !

    Hi,
    all my hosts/services are passively checked. I defined a service check_period and notification_period attributes as copied hereunder ... as a sum-up :
    - service template defines a check_period and a notification_period as Monitoring-workhour (from 8:00 to 21:00 every day ...)
    - service defines a notification_period as 24x7

    Whenever the service state changes? I always receive a notification wether I am in the check_period or not !

    As far as I understood Nagios/Shinken configuration, the service state modifications should not raise a notification when I am not in a check_period ? Even if I am currently in the notification_period ...

    Thansk for your help to confirm my analysis or to explain what is bad in my configuration ...

    Best regards, Fred

    [tt]

    define service{
    use template4-service
    host_name fvc318
    service_description nsca_cpu
    _ITEMSID 366
    _ITEMTYPE service
    check_freshness 1
    freshness_threshold 600
    check_command check_dummy!2!No data for CPU
    contacts monitoring
    notification_period 24x7
    notification_interval 720
    icon_set service
    action_url http://shinken/pnp4nagios/index.php/graph?host=$HOSTNAME$&srv=$SERVICEDESC$
    }


    define service{
    name template4-service
    check_interval 60
    retry_interval 1
    max_check_attempts 1
    check_period Monitoring-workhour
    notification_interval 30
    notification_period Monitoring-workhour
    notification_options w,u,c,r,f,s
    process_perf_data 1
    active_checks_enabled 0
    passive_checks_enabled 1
    parallelize_check 1
    obsess_over_service 1
    check_freshness 1
    freshness_threshold 3600
    notifications_enabled 1
    event_handler_enabled 0
    flap_detection_enabled 1
    failure_prediction_enabled 1
    retain_status_information 1
    retain_nonstatus_information 1
    is_volatile 0
    _httpstink NO
    register 0
    icon_set service
    action_url http:///pnp4nagios/index.php/graph?host=$HOSTNAME$&srv=$SERVICEDESC$
    }

    [/tt]

  2. #2
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,130

    Re: Passive service checks / check_period / notification_period conflict !

    No, the notification raise is still there. That's the default behavior since Nagios, but it's true that receive a notification when the check_period is off is a bit strange. Can you open a ticket for this? Can be a good feature.
    No direct support by personal message. Please open a thread so everyone can see the solution

  3. #3
    Member
    Join Date
    May 2013
    Location
    France - Valence
    Posts
    91

    Re: Passive service checks / check_period / notification_period conflict !

    Hi,
    I opened an issue (#1046) and posted a fix proposal in the shinken fork for Glpi Monitoring (https://github.com/mohierf/shinken/c...16dfca95bc5d78)

    I would appreciate if you had few minutes to hav a look at my fix :-)

    BR, Fred

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •