Hi @Aliabbas_Fazal, I can update you on a few things around this area of the NR platform.
The title of this thread focuses on not receiving notifications during certain times of day. There are a few ways to approach this problem. As someone pointed out putting schedules on conditions is one way, however I’m not sure this is the best approach due to the large increase in condition configuration and ongoing management complexity it introduces.
We think modern baselines is the ideal approach to this problem. A system that models past behaviors, accommodates for trends and weekly seasons/cycles is a simpler more flexible approach to alerting on these tricker KPIs.
Additionally there are times when teams need to do maintenance on a system that will likely cause crazy things to happen to the data collected. One comment above mentioned nightly database dumps that make i/o and other measure emit wonky values during the backup. Recurring and one time maintenance windows is the solution we want to introduce for this. Basically being able to choose entities in NR and associate it with a window of time where notifications should not be sent.
It is possible to solve for this using our APIs and cron jobs today, but a native solution is really the most efficient way to do this. Defining windows like this in Alerts is high priority and I hope to be able to share some more information on this effort soon.