-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Proposal for Exposing Storage Metrics #855
Conversation
7de62b2
to
31f6aad
Compare
cc @kubernetes/sig-instrumentation-feature-requests @kubernetes/sig-storage-feature-requests |
|
||
| Metric name | Metric type | Labels/tags | | ||
|-------------|-------------|-------------| | ||
| volume_stats_capacityBytes | Gauge | namespace=\<persistentvolumeclaim-namespace\> <br/> persistentvolumeclaim=\<persistentvolumeclaim-name\> <br/> persistentvolume=\<persistentvolume-name\> | |
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.
mixed snake and camel case
} | ||
|
||
// PVCReference contains enough information to locate the referenced PVC. | ||
type PodReference struct { |
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.
Comment says PVCReference, struct name is PodReference
} | ||
|
||
// PVReference contains enough information to locate the referenced PV. | ||
type PodReference struct { |
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.
comment says PVReference, struct name is PodReference
|
||
|
||
## Goals | ||
The gola of this proposal is to expose storage usage metrics to users for monitoring their storage systems. |
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.
Is this feature on pod-level ?
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 think the metric is per volume. Could you explain what you mean by "pod-level"?
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.
spell: s/gola/goal/
Automatic merge from submit-queue Proposal for adding PVC info to VolumeStats Flushes out details for part 1 of the changes described in [#855](#855) Feature: [#363](kubernetes/enhancements#363)
Automatic merge from submit-queue Expose PVC metrics via kubelet prometheus This depends on #51448, opening early though. second commit is mine and mostly a copy/paste job. implements metrics listed in here kubernetes/community#855 following method here kubernetes/community#930 (comment) **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: kubernetes/enhancements#363 **Special notes for your reviewer**: **Release note**: ```release-note PersistentVolumeClaim metrics like "volume_stats_inodes" and "volume_stats_capacity_bytes" are now reported via kubelet prometheus ```
Is this ready for review? I still can see |
|
||
### volume usage information indexed by PVC/PV in Kubelet Summary API | ||
|
||
The basic idea is to cache PVC and the volume information in kubelet volume manager which is similar to caching the pod and volume information. In Summary API, In Summary API, we could add PVC and PV references into VolumeStats which is included in PodStats. |
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.
nit: double "In Summary API"
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.
nit: incomplete sentence? "The second part is to register the volume metrics to ."
Flushes out details for part 1 of the changes described in kubernetes#855 Feature: kubernetes/enhancements#363
Flushes out details for part 1 of the changes described in kubernetes#855 Feature: kubernetes/enhancements#363
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Flushes out details for part 1 of the changes described in kubernetes/community#855 Feature: kubernetes#363
Automatic merge from submit-queue Proposal for adding PVC info to VolumeStats Flushes out details for part 1 of the changes described in [kubernetes#855](kubernetes/community#855) Feature: [kubernetes#363](kubernetes#363)
Status? |
👍 I'd like to view how much of a persistent volume is in use and don't know of a way. |
Flushes out details for part 1 of the changes described in kubernetes/community#855 Feature: kubernetes/enhancements#363
Automatic merge from submit-queue Proposal for adding PVC info to VolumeStats Flushes out details for part 1 of the changes described in [#855](kubernetes/community#855) Feature: [#363](kubernetes/enhancements#363)
Flushes out details for part 1 of the changes described in kubernetes/community#855 Feature: kubernetes/enhancements#363
Flushes out details for part 1 of the changes described in kubernetes/community#855 Feature: kubernetes/enhancements#363
Automatic merge from submit-queue Proposal for adding PVC info to VolumeStats Flushes out details for part 1 of the changes described in [#855](kubernetes/community#855) Feature: [#363](kubernetes/enhancements#363)
Flushes out details for part 1 of the changes described in kubernetes/community#855 Feature: kubernetes/enhancements#363
Automatic merge from submit-queue Proposal for adding PVC info to VolumeStats Flushes out details for part 1 of the changes described in [#855](kubernetes/community#855) Feature: [#363](kubernetes/enhancements#363)
Flushes out details for part 1 of the changes described in kubernetes/community#855 Feature: kubernetes/enhancements#363
Automatic merge from submit-queue Proposal for adding PVC info to VolumeStats Flushes out details for part 1 of the changes described in [#855](kubernetes/community#855) Feature: [#363](kubernetes/enhancements#363)
Flushes out details for part 1 of the changes described in kubernetes/community#855 Feature: kubernetes/enhancements#363
Automatic merge from submit-queue Proposal for adding PVC info to VolumeStats Flushes out details for part 1 of the changes described in [#855](kubernetes/community#855) Feature: [#363](kubernetes/enhancements#363)
Flushes out details for part 1 of the changes described in kubernetes/community#855 Feature: kubernetes/enhancements#363
Automatic merge from submit-queue Proposal for adding PVC info to VolumeStats Flushes out details for part 1 of the changes described in [#855](kubernetes/community#855) Feature: [#363](kubernetes/enhancements#363)
This proposal is exploring ways of exposing storage metrics to users