-
Notifications
You must be signed in to change notification settings - Fork 99
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
Metrics-ingest-delay bugfix #151
Conversation
Signed-off-by: eitah <eli@spantree.net>
Signed-off-by: eitah <eli@spantree.net>
Alphabetize readme Signed-off-by: eitah <eli@spantree.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, this makes sense. Add()
only returns a new value, it doesn't manipulate the state of the Time.
The linter is having trouble, will figure it out. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oups! I missed that somehow. Thanks for fixing it.
I fixed the linting issue in HEAD. Going to merge this. |
We noticed that with
metrics-ingest-delay
flag set the exporter fails to apply the time offset as expected, despite what the debug log prints. The root cause appears to be failing to assign back the start and end times back to the original target as indicated in my PR below.I've dropped the fmt.Printf statements that allowed us to locate the bug, but feel free to revert my second commit locally to reproduce the issue. You might need to change the IF conditional from Stored bytes, a BigQuery metric, to another similar metric depending on what project you use for testing and what APIs you have available there.
I also added the feature to the README since it seems to be good to go otherwise!