You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
The escalation step's wording says that it uses UTC timezone. In PUT request on updating time range and in escalation logs I can see that the time range for this step is different than I selected in the step settings.
How do we reproduce it?
Set non-UTC local timezone
Create escalation step "Continue escalation if current time is in range"
Select time range in local timezone, that doesn't cover current time
Send demo alert in any integration using escalation chain with this step
Check escalation timeline
Grafana OnCall Version
r213-v1.3.23
Product Area
Alert Flow & Configuration
Grafana OnCall Platform?
I use Grafana Cloud
User's Browser?
No response
Anything else to add?
No response
The text was updated successfully, but these errors were encountered:
FWIW, besides the UI and logs mentioning expected UTC times, public API also expects UTC values for from/to.
As noted, the conversion is being done in the frontend before pushing the data, so I think we should disable this TZ conversion there and be consistent with the expectations everywhere else (or alternatively, make sure to display in the UI which is the timezone assumed before the conversion).
What went wrong?
What happened:
The escalation step's wording says that it uses UTC timezone. In PUT request on updating time range and in escalation logs I can see that the time range for this step is different than I selected in the step settings.
How do we reproduce it?
Grafana OnCall Version
r213-v1.3.23
Product Area
Alert Flow & Configuration
Grafana OnCall Platform?
I use Grafana Cloud
User's Browser?
No response
Anything else to add?
No response
The text was updated successfully, but these errors were encountered: