-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[servicegraphconnector] Add flush interval config #27879
[servicegraphconnector] Add flush interval config #27879
Conversation
|
||
// Metrics are not immediately flushed | ||
assert.Len(t, metricsExporter.md, 0) | ||
time.Sleep(time.Second * 5) |
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.
Can you do a smaller flush interval for this test and use assert. Eventually here? Otherwise, the test will take at least 5 seconds to run. Seen individually, it's not a huge problem, but on the bigger context, it might cause our CI to take longer and longer :-/
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.
Changed!
**Description:** Add a config option to periodically flush metrics, instead of flushing on every push. **Link to tracking Issue:** <Issue number if applicable> open-telemetry#27679 **Testing:** <Describe what testing was performed and which tests were added.> Added tests that verify metrics are flushed asynchronously **Documentation:** <Describe the documentation added.> Documentation added to `config.go` --------- Co-authored-by: Juraci Paixão Kröhling <juraci@kroehling.de>
**Description:** Add a config option to periodically flush metrics, instead of flushing on every push. **Link to tracking Issue:** <Issue number if applicable> open-telemetry#27679 **Testing:** <Describe what testing was performed and which tests were added.> Added tests that verify metrics are flushed asynchronously **Documentation:** <Describe the documentation added.> Documentation added to `config.go` --------- Co-authored-by: Juraci Paixão Kröhling <juraci@kroehling.de>
…opy configuration README (#29919) **Documentation:** <Describe the documentation added.> #27879 recently added a new configuration option to the `servicegraph` components called `metrics_flush_interval`. I noticed this wasn't documented for either component, and the `connector/servicegraph` README doesn't include a configuration section. Since the connector is just a wrapper of the processor at this point, I cleaned up the processor's configuration section and copied it to the connector, adding an entry for the new `metrics_flush_interval` option.
…opy configuration README (open-telemetry#29919) **Documentation:** <Describe the documentation added.> open-telemetry#27879 recently added a new configuration option to the `servicegraph` components called `metrics_flush_interval`. I noticed this wasn't documented for either component, and the `connector/servicegraph` README doesn't include a configuration section. Since the connector is just a wrapper of the processor at this point, I cleaned up the processor's configuration section and copied it to the connector, adding an entry for the new `metrics_flush_interval` option.
Description: Add a config option to periodically flush metrics, instead of flushing on every push.
Link to tracking Issue: #27679
Testing: Added tests that verify metrics are flushed asynchronously
Documentation: Documentation added to
config.go