Notification Alerts for Issues Persisting at the Start of Time Periods
1
votes
At present, the notification system functions within a defined time window (9:00 to 17:00), which means that if a service issue arises outside this window (e.g., at 20:00), no notification is triggered.
Request: Optional Notification Trigger
New Requirement: If a service is still in an issue state at the start of the notification window (e.g., 9:00), a notification should be sent since the issue persists as the notification period commences.
Current Workaround:
Recurring downtimes are being utilized instead of utilizing a time period for notifications.
Implementing this new option would streamline the process and eliminate the need for recurring downtimes.
Best regards.