-
Notifications
You must be signed in to change notification settings - Fork 86
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
Report schedule local time support #1258
Comments
@chancez am i right to ask you for help on such 'report time' related case ? |
@suridaddy Chance does not work for RHT anymore... @timflannagan1 can you help answer @suridaddy's question? Thanks! |
@suridaddy sorry for the slow response, I've been pretty tied up recently - in terms of any localized TZ support, I'm not aware of any. I believe we do all of the UTC timestamp processing as cron expressions under-the-hood. Can you tell me more about why you wouldn't be able to use the |
@timflannagan1 sorry, i didn't notice your message, and sorry for late response. Let me explain more as below,
Freely let me know if it's not clear, thanks. |
Environment:
Description
Metering report is leveraged by us to generate daily, weekly and monthly report, and we found that the report always generated at UTC 0:0:0 time.
It's expected to generate the report at local time(Asia/Shanghai, UTC+8) 0:0:0. For the daily and weekly report, we can leverage the 'hour' setting(set
hour: 16
of the day, or last day of week).For the monthly report, it's hard to know what's the last day of the month, so, the workaround doesn't work.
My question:
is it possible to make the report generated using local time 0:0:0? do we have a way to set the timezone info to the reporting-operator pod/container, or set timezone info to the report definition?
The text was updated successfully, but these errors were encountered: