-
Notifications
You must be signed in to change notification settings - Fork 134
minimal example of working metrics #783
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
base: master
Are you sure you want to change the base?
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: iamkirkbater The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
A minimal working example of metric collection using iamkirkbater/cobra-otel-metrics.
Marking this as a draft as I'd still like to finish adding some functionality to the cobra-otel-metrics package itself around the opt-in data controls. Additionally I'd like to get a working HTTP or GRPC collector working and test this "over the net". This is currently using a
stdoutexporter, which just creates a bunch of, what would be best considered "noise" to the average person, but here is what the metric would look like for aosdctl cluster context --cluster-idcommand invocation: