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
Comments
@bernd is there a possibility of getting some traction on the associated requests given we have a paying customer asking for it? |
@bernd bumping again. I know you closed this, but I've not seen any activity on the other 2 issues you linked to. |
@dennisoelkers do we have any movement on this? We have another different customer asking us about this issue. |
todvora
added a commit
that referenced
this issue
Dec 3, 2021
9 tasks
dennisoelkers
pushed a commit
that referenced
this issue
Dec 6, 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>
Not completely fixed in #11734, just the export part. |
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
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>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: