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
I guess if your server has its time hardcoded Europe/Berlin then the Python client may not be able to get the correct datetime.utcnow()? I'm not sure how that works.
I'm experimenting with this on a baremetal cluster whose nodes have a timezone configured. (UTC +1, Europe/Berlin)
The issue I'm seeing is that events get added in Sentry with a delay of that one hour (it realizes the event is an hour old, though).
Is this something that could be fixed by configuration, or is UTC a requirement for the kubernetes nodes?
The text was updated successfully, but these errors were encountered: