-
Notifications
You must be signed in to change notification settings - Fork 821
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
feat(sdk-metrics-base) Add pull controller #2517
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Why is
collect
public? I don't see it called anywhere. Is it expected to be called by exporters? If so, isn't it a little odd that calling the controller causes the controller to call the exporter? Seems like an unnecessarily convoluted export chain.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.
It was to keep implementing a push-based versus pull-based exporter very similar, only difference being the added function registerPullCollector and having the exporter invoke the collect function itself
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.
Have you looked at implementations in other languages like python and go to see what they're doing?
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.
Haven't really looked around much as I found your comment and figured that sounded pretty simple :) I will take a look around if I find the time.
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.
I had a look at the Go implementation (https://github.com/open-telemetry/opentelemetry-go/blob/main/sdk/metric/controller/basic/controller.go)
They have a single Controller that has (among others)
Start
,Collect
andForEach
exposed -Start
starts the periodic calling ofCollect
whereasCollect
itself collects the metrics and pushes them to the exporter (if one is defined), so basically the same pattern as above.ForEach
"calls the passed function once per instrumentation library, allowing the caller to emit metrics grouped by the library that produced them."They differ in that I do not see a way for the exporter to obtain a handle on the Collector (as I've done through the registerPullController function) - Indeed, the Go Prometheus Exporter explicitly states it does not implement the metric.Exporter interface, but instead itself creates a pull controller (https://github.com/open-telemetry/opentelemetry-go/blob/main/exporters/prometheus/prometheus.go#L41) and calls Collect, followed by ForEach whenever the HTTP endpoint is invoked.
If we were to follow their design more closely, we should have one Collector with public Start, Collect and ForEach methods. I do not see a simple way other than the aforementioned
registerPullController
to expose a handle to the Collector though - What the Go Prometheus Exporter does is basically set its internal Controller as the MetricsProvider, but we do not expose that as an option in the NodeSDKConfiguration.