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

Promtail timezone stage doesn't work well on Windows #1361

Closed
slim-bean opened this issue Dec 4, 2019 · 6 comments · Fixed by #3332
Closed

Promtail timezone stage doesn't work well on Windows #1361

slim-bean opened this issue Dec 4, 2019 · 6 comments · Fixed by #3332
Labels
keepalive An issue or PR that will be kept alive and never marked as stale.
Milestone

Comments

@slim-bean
Copy link
Collaborator

This looks to be the result of: golang/go#21881

There are a few options on that page, I'm inclined towards just embedding the timezone data into the binary itself for all our builds (we could then remove it from the promtail docker image), looks like it would add about another 1MB to the binary size (which is already 60MB? 80MB?)

This has the issue that it will likely never get updated unless someone specifically finds a bug and updates it manually... (We should have a makefile target which at least makes this easy to do)

IMO it's better than asking people to download a zip file and set environment variables (or install Go) is a worse alternative.

Thoughts anyone?

@tdabasinskas
Copy link

For me, embedding the timezone data into the windows image makes sense. Even if it increases the binary size by 1MB (I think it's actually ~800KB or so), it's better than having the users to sped time troubleshooting the reason timezone stage does not work or/and getting the the zip on machines manually.

@pstibrany
Copy link
Member

There are discussions on that issue about using data that's already available on Windows. Perhaps we can wait until it gets fixed? It's not like there are no workarounds today:

Or set the %ZONEINFO% environment variable to point to your shipped zoneinfo.zip.

(golang/go#21881 (comment))

This looks like a good solution until it's fixed properly. (But we should document it for Windows users)

@stale
Copy link

stale bot commented Jan 11, 2020

This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale A stale issue or PR that will automatically be closed. label Jan 11, 2020
@slim-bean slim-bean added the keepalive An issue or PR that will be kept alive and never marked as stale. label Jan 13, 2020
@stale stale bot removed the stale A stale issue or PR that will automatically be closed. label Jan 13, 2020
@cyriltovena
Copy link
Contributor

This should be possible now that go 1.15 is merged. #2877

cyriltovena added a commit to cyriltovena/loki that referenced this issue Feb 12, 2021
cyriltovena added a commit that referenced this issue Feb 16, 2021
Fixes #2995
Fixes #1361

Signed-off-by: Cyril Tovena <[email protected]>
cyriltovena pushed a commit to cyriltovena/loki that referenced this issue Jun 11, 2021
…-retries

Use a rate-limiter to back off on DynamoDB throttling
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keepalive An issue or PR that will be kept alive and never marked as stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants