search

grafana / oncall

Developer-friendly incident response with brilliant Slack integration
GNU Affero General Public License v3.0
3.48k stars 286 forks source link

OnCall reporting unassigned time period in the past #1108

Open armandgrillet opened 1 year ago

armandgrillet commented 1 year ago

I have updated an on-call rotation at 10AM today (Jan 9th), there is no no one on-call until 4AM which is the past. However, OnCall is regularly (~every hour) complaining now:

SS 2023-01-09 at 14 07 35

This alert message is not useful as this only concerns the past.

thomasmitchell commented 1 year ago

I have also been running into this issue. It seems like new schedules get marked with this error, but the warning goes away the next day. However, it only posted the message once per schedule - when they were created. I didn't get a good idea of when exactly the schedule stopped having its warning state, but it hasn't been 24 hours since many of those schedules were created. May have had something to do with the UTC day cutoff.

thomasmitchell commented 1 year ago

It may also have something to do with it having been a Monday, because schedules I'm creating today aren't having this issue, and the issue was also originally reported on a Monday.