Open RainerGoermann opened 4 years ago
@RainerGoermann Thank you for writing to us.
@RainerGoermann Possibly the API for the monitors will help with your specific request (https://documenter.getpostman.com/view/631643/JsLs/?version=latest#86a64793-eb15-d40f-18aa-f74a666a6130), although having UI is definitely a better solution.
However that API also has limitations that we'd like to see removed, like currently we are not working on Fridays, meaning all our services on Dev, Test, etc. are shut down and there is no way to stop monitors from running just on Friday, as using cron "0 0 9 MON-THU" produces error response: "The specified cron pattern is not allowed. Please check https://monitor.getpostman.com for the allowed schedules."
In addition, I would like to be able to set the hour too, so I can schedule monitor runs and distribute them more evenly. The API already accepts a cron, but it returns an error as described above.
Is your feature request related to a problem? Please describe. On the "Edit monitor" page in the area "Schedule" it is at the moment only possible to set the type of timer (houerly, weekly, ...) and the frequence (Every x minutes). This way it is unfortunately not possible to either add a range where the monitoring should be executed or be paused, like only execute between 0800 and 1400 or execute the runs more precise like at minute **:20.
Describe the solution you'd like In our case it would be nice, if we could have more cron like functionality (https://en.wikipedia.org/wiki/Cron), what means that it would be nice to have an "Advanced" area inside/underneath the "Schedule" area to add a cron like expression to execute the monitoring runs more precise.
Describe alternatives you've considered At a minimum it would be good to add fields for an execution range (Execution start: 08:00; Execution end: 22:00)
Additional context Monitoring is important. But not allways 24/7. Every request that can be saved counts. Each request is even reducing carbon dioxide. ;)