Shinken timeperiods build ...

[mohierf]

! This issue is currently for tracking / testing purposes ...

Shinken contacts :

• host :
  • if no contacts defined in CC, use default contact (monitoring) if configured
• service :
  • if no contacts defined in CC, use default contact (monitoring) if configured

Glpi / monitoring calendars :

• (1) : host check component control period
• (2) : component control period

Shinken timeperiods/intervals/options :

• host :
  • check_period : (1)
  • host notification_period : default Shinken parameter (24x7)
  • host notification_interval : component catalog interval
  • host notification_options : default Shinken parameter (d,u,r,f,s)
• service :
  • check_period : (2)
  • service notification_period : default Shinken parameter (24x7)
  • service notification_interval : component catalog interval
  • service notification_options : default Shinken parameter (w,u,c,r,f,s)
• service template :
  • check_period : (2)
  • service notification_period : default Shinken parameter (24x7)
  • service notification_interval : component catalog interval
  • service notification_options : default Shinken parameter (w,u,c,r,f,s)

[mohierf]

Host check_period :

• the host check command is fetched from the component defined in the monitoring tab of an entity. As of it, the host check_period is built from the component calendar and the entity jetlag.

Host notifications :

• the host notification_period and notification_options are the default Shinken parameters in shinken.class.php
• the host notification_interval is defined in the component catalog

Service notifications :

• the service notification_period and notification_options are the default Shinken parameters in shinken.class.php
• the service notification_interval is defined in the component catalog

---

As of it, it is not possible to manage correctly the shinken notifications on host/service levels ... it is always managed on a contact level ...

For instance, if a contact is configured to receive host DOWN notifications, he will receive all hosts notifications because it is not possible to define that DOWN notifications will not be sent for a specific host or hostgroup !

[mohierf]

With my new modifications :

• add links to two contact templates in computer catalog

• new Shinken build function

  It is possible to define (in CC) an host notification template and a service notification template.

Host notifications, got from contact template :

• enabled/disabled
• notification_period and notification_options

Service notifications, got from contact template :

• enabled/disabled
• notification_period and notification_options

---

It will be necessary to create and manage a new host notification and a new service notification class and objects for these notifications !