Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timezone offset #19

Closed
tkuther opened this issue Feb 21, 2019 · 2 comments
Closed

Timezone offset #19

tkuther opened this issue Feb 21, 2019 · 2 comments

Comments

@tkuther
Copy link

tkuther commented Feb 21, 2019

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?

@bretthoerner
Copy link
Contributor

All events should be sent in UTC time so that they can then be displayed based on the user's timezone settings here: https://sentry.io/settings/account/details/

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.

@tkuther
Copy link
Author

tkuther commented Feb 21, 2019

Fixed. The solution was to set TZ environment variable in the sentry-kubernetes container.

@tkuther tkuther closed this as completed Feb 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants