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

Track PVC bound time in volume populator #174

Open
Rishita-Golla opened this issue Nov 14, 2024 · 1 comment
Open

Track PVC bound time in volume populator #174

Rishita-Golla opened this issue Nov 14, 2024 · 1 comment

Comments

@Rishita-Golla
Copy link

Description

Currently, the volume populator library lacks a metric to track the time it takes for a PVC to transition to the "bound" state. This metric would be valuable for understanding volume provisioning performance.

Proposed Solution

Introduce a new metric within the volume populator library that measures the time elapsed between the following events:
Start Time: When the volume populator begins processing a PVC request. This might not align with the PVC creation time, especially for populators using the WaitForFirstConsumer binding mode.
End Time: When the PVC reaches the "bound" state, indicating successful binding to a PersistentVolume (PV).

This metric provides insights into the efficiency of volume provisioning. Increased PVC bound times could signal underlying issues with storage provisioning or the volume populator itself. This metric is relevant across all volume populator types and is not specific to any particular storage backend.

@sunnylovestiramisu
Copy link
Contributor

sunnylovestiramisu commented Jan 2, 2025

Note: this is a feature request of adding kube_state_metrics but NOT required for GA for lib-volume-populator.

Also "how long it takes for a pvc to be bound" is generic and not specific to lib-volume-populator. A discussion is needed for where to add such metrics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants