Skip to content
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 additional metrics guideline violations to metrics overhaul #655

Merged
merged 2 commits into from
Dec 20, 2018

Conversation

brancz
Copy link
Member

@brancz brancz commented Dec 15, 2018

While looking into the kubelet API, I noticed the existance of the /metrics/probes endpoint, and noticed it violates the instrumentation guidelines in the same way as the cAdvisor labels do. Therefore adding those to the metrics overhaul KEP.

@DirectXMan12 @ehashman @mxinden @piosz @coffeepac @s-urbaniak @metalmatze

@k8s-ci-robot k8s-ci-robot added kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. labels Dec 15, 2018
@k8s-ci-robot k8s-ci-robot added sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. approved Indicates a PR has been approved by an approver from all required OWNERS files. sig/pm size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Dec 15, 2018
@@ -96,6 +96,10 @@ https:/kubernetes/kubernetes/issues/68522

https:/kubernetes/kubernetes/pull/63924

#### Prober metrics

Make proper metrics introduced in https:/kubernetes/kubernetes/pull/61369 conform to the Kubernetes instrumentation guidelines.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Make proper metrics introduced in https:/kubernetes/kubernetes/pull/61369 conform to the Kubernetes instrumentation guidelines.
Make prober metrics introduced in https:/kubernetes/kubernetes/pull/61369 conform to the Kubernetes instrumentation guidelines.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@brancz -- could you link out to the instrumentation guidelines here as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@ehashman
Copy link
Member

LGTM; I realized today I had also included this in kubernetes/kubernetes#69099 and I've updated the PR to reflect that.

@brancz
Copy link
Member Author

brancz commented Dec 18, 2018

@ehashman awesome!

@justaugustus
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 20, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brancz, justaugustus

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit d6510e0 into kubernetes:master Dec 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants