-
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
fix(outputs.prometheus_client): Ensure v1 collector data expires promptly #14232
Conversation
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.
While the code looks good as-is I do have one suggestion. Feel free to ignore @powersj!
@srebhan ready for another round. thanks! |
…ptly The expirey timer can overlap with each collection interval. Meaning that duplicate data can appear. What the v2 collector does is run expire function at every add and collect to avoid any overlap or non-new data. fixes: influxdata#14230
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
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.
Wow I really love this @powersj! Thanks!
The expire timer can overlap with each collection interval. Meaning that duplicate data can appear. What the v2 collector does is run expire function at every add and collect to avoid any overlap or non-new data.
fixes: #14230