-
Notifications
You must be signed in to change notification settings - Fork 264
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
Add protocol to Metric Configuration Service #183
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.
Please split the PR:
- Delete all generated files
- Rest of changes for the experimental feature
I pressed the magic button to update the branch and things are good now
@bogdandrutu Great thanks! The local setup was a little weird, since we based our changes off the 0.4.0 release to avoid dependency problems in our prototypes. Sorry I missed your earlier message! I went ahead and straightened out the history for this PR and force-pushed the changes. |
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.
LGTM thanks!
// MetricConfig is a service that enables updating metric schedules, trace | ||
// parameters, and other configurations on the SDK without having to restart the |
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.
// MetricConfig is a service that enables updating metric schedules, trace | |
// parameters, and other configurations on the SDK without having to restart the | |
// MetricConfig is a service that enables updating metric schedules and other configurations on the SDK without having to restart the |
Looks like the scope was narrowed to just metrics which makes sense
|
||
syntax = "proto3"; | ||
|
||
package opentelemetry.proto.experimental.metricconfigservice; |
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.
add this in:
"experimental/metrics/configservice"
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.
Done
Thank you for initiating the experimental folder! |
Changes
Goal
We introduce a new protocol for dynamically configuring metric collection schedules. It follows from this OTEP.
An example implementation is almost completed and will be sent to the collector-contrib and go-contrib repos. In the meantime, we'd love to hear your thoughts on this protocol and the related specification!
About
We're an intern group at Google. Members include: