-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Add date offset option to date processor #6886
Conversation
Uh oh, it appears we have been setting the tag based on the local system time instead of using UTC to match the metric timestamps. I will fix this but it will not be fully backwards compatible. |
Are you sure it is correct? Most people use this plugin to put tag offset appropiate to their timezone. |
I believe your calculation is correct. My line of thinking here is that metrics are always reported in UTC, and adding a tag with a 0 offset should match the timestamp in the database, no matter the timezone of the system who collected it.
I don't have a good way to judge this. I suspect the primary use of this plugin is to insert day of the week or month of the year, and it is possible that many users haven't noticed the discrepancy. This would be a change of behavior though, so at the very least we should add this to the release notes. |
Ok, now I understand it. One more thing I can add to this discussion is a RTC time - reference time which may be used on linux with i.e. timedatectl. It lets you set hardware time to UTC or local. You may also consider to put an information about that and let the user choose the best solution for use. |
70be89e
to
04c38d5
Compare
Rebased on master due to CHANGLOG.md conflict. Added new |
closes: #6877
Required for all PRs: