Open s-duret opened 9 years ago
Hi,
The behavior you are describing is already the one implemented centreon-engine. I tested it for good conscience. Both the unit tests and a manual test were successful.
Have you an example of any case where it doesn't work as expected?
Regards,
Hi,
Please take a look on screenshot in attachment.
My configuration:
The first notification in the escalation period should be around 10:00 or 10:05 (because interval is 5 minutes) but it's sended at 10:29 (because last notification is 30 minutes before).
Regards
Hello,
It could be great that notification's interval of a service will not be acknowledged when the service enters in escalation's period.
For example: I have a service who notifies contacts every two hours and a esclalation who notifies every 5 minutes. The escalation begins at 10:00 and the last notificaton of my service sended at 9:30. Currently, the next notification will not be sended at 10:00 but at 11:30, I think it's a problem and it could be an enhancement for the next version.
Regards,