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

Generate reports and CSVs in local time #9546

Closed
asachs01 opened this issue Nov 18, 2020 · 5 comments · Fixed by #11734
Closed

Generate reports and CSVs in local time #9546

asachs01 opened this issue Nov 18, 2020 · 5 comments · Fixed by #11734

Comments

@asachs01
Copy link

What?

As a user, I know that the values I see for log timestamps in my browser are localized to my browser's time. This differs when I generate a report or a CSV, as those values show system time or UTC (z-4329). I'd like to have the option to generate reports/CSVs in my local time, versus system time.

@bernd
Copy link
Member

bernd commented Nov 19, 2020

Duplicate of #4523 and related to #8011.

@bernd bernd closed this as completed Nov 19, 2020
@asachs01
Copy link
Author

@bernd is there a possibility of getting some traction on the associated requests given we have a paying customer asking for it?

@asachs01
Copy link
Author

asachs01 commented Dec 2, 2020

@bernd bumping again. I know you closed this, but I've not seen any activity on the other 2 issues you linked to.

@ed-graylog
Copy link

@dennisoelkers do we have any movement on this? We have another different customer asking us about this issue.

@todvora todvora self-assigned this Dec 3, 2021
janheise pushed a commit that referenced this issue Dec 7, 2021
* Add backend support for user-defined TZ in reports #9546

* Use current user's timezone if none is specified for export.

* Falling back to UTC if user has no timezone configured.

* Using better syntax to handle optional fields for builder.

* Defining default time zone for export command.

* Use quite unique timezone to test TZ configuration in exports

Co-authored-by: Dennis Oelkers <dennis@graylog.com>
@dennisoelkers
Copy link
Member

dennisoelkers commented Dec 7, 2021

Not completely fixed in #11734, just the export part.

@dennisoelkers dennisoelkers reopened this Dec 7, 2021
linuspahl pushed a commit that referenced this issue Dec 13, 2021
* Add backend support for user-defined TZ in reports #9546

* Use current user's timezone if none is specified for export.

* Falling back to UTC if user has no timezone configured.

* Using better syntax to handle optional fields for builder.

* Defining default time zone for export command.

* Use quite unique timezone to test TZ configuration in exports

Co-authored-by: Dennis Oelkers <dennis@graylog.com>
@todvora todvora removed their assignment Dec 13, 2021
linuspahl pushed a commit that referenced this issue Dec 13, 2021
* Add backend support for user-defined TZ in reports #9546

* Use current user's timezone if none is specified for export.

* Falling back to UTC if user has no timezone configured.

* Using better syntax to handle optional fields for builder.

* Defining default time zone for export command.

* Use quite unique timezone to test TZ configuration in exports

Co-authored-by: Dennis Oelkers <dennis@graylog.com>
@linuspahl linuspahl self-assigned this Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants