search

centreon / centreon-archived

Centreon is a network, system and application monitoring tool. Centreon is the only AIOps Platform Providing Holistic Visibility to Complex IT Workflows from Cloud to Edge.
https://www.centreon.com
GNU General Public License v2.0
575 stars 240 forks source link

different monitoring policy for the same resource #6536

Open dellarte opened 6 years ago

dellarte commented 6 years ago

BUG REPORT INFORMATION

Centreon Web version: 2.8.24

Centreon Engine version: 1.8.1

Centreon Broker version: unknow

OS: CentOS release 6.10 (Final)

Additional environment details (AWS, VirtualBox, physical, etc.): Appliance dowloaded from Centreon Website

Steps to reproduce the issue:

  1. Add a CPU check for the server "X" on a service "CPU working hours" for the period 09:00-18:00
  2. Add a CPU check for the same server "X" on a service "CPU non working hours" for the period 18:01-08:59
  3. Generate high CPU utilization for both period on server "X"

Describe the results you received: In the monitoring section, I get the alert for both "CPU working hours" and "CPU non working hours" no matter the period we are currently. Ineed, it keep the last check (which failed) in memory... (e.g.: It's 13:20, and i have an alert (not notification) for the service which it should be controlled by night) capture

Describe the results you expected: In the monitoring section, when I'm checking alerts, I would like to have only the alerts for the current period. Or any alternative to implement a different checking regarding the period

Additional information you think important (e.g. issue happens only occasionally): I've created 2 services by checks because we don't have the same checking policy during work and non work hours.

lpinsivy commented 6 years ago

Hi @dellarte display only issue on specific timeprriod is a workaround.

As you said the best way is to add to different policies. We keep it in mind.

Regards,