-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
servicegraph connector: Add metrics_flush_interval #27679
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Sounds like a valid feature request to me. However, I looked into the implementation side of things and it looks like the servicegraph connector is really just a wrapper of the servicegraph processor, which is actually now deprecated. This means all of the logic being used is the processor's functionality. It would be a pretty involved change since these two components are so heavily intertwined. I'll defer to code owners to decide what the best path forward is here. |
Pinging code owners for processor/servicegraph: @jpkrohling @mapno. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
**Description:** Add a config option to periodically flush metrics, instead of flushing on every push. **Link to tracking Issue:** <Issue number if applicable> #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>
**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>
We really should have it the other way around, with the connector being the reference implementation, and the processor wrapping it. |
@gouthamve @mapno Can this issue be closed now, given that #27879 was merged? |
Component(s)
connector/servicegraph
Is your feature request related to a problem? Please describe.
spanmetrics connector has a
metrics_flush_interval
that controls how frequently metrics are pushed. Service graph connector should have the same.Describe the solution you'd like
Add
metrics_flush_interval
to service graph connector.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: