You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the solution you would like.
Currently, we lack information about the size of the OVF cache used during VM image reconciliation. It would be beneficial to add logs that provide this information when updating the cache here:
Is there anything else you would like to add?
This may also require a function added in the Cache to expose the size of its items.
Additionally, we should emit prometheus metrics for total number of cached items which can help root cause issues that result in the VM operator pod running out of memory.
Please tell us about your environment.
N/A
The text was updated successfully, but these errors were encountered:
aruneshpa
changed the title
Add logs to emit total number of OVF cached items
Add metrics and logs to emit total number of OVF cached items
Jan 4, 2024
Please describe the solution you would like.
Currently, we lack information about the size of the OVF cache used during VM image reconciliation. It would be beneficial to add logs that provide this information when updating the cache here:
vm-operator/pkg/vmprovider/providers/vsphere/vmprovider.go
Lines 287 to 288 in f4257d2
Is there anything else you would like to add?
This may also require a function added in the Cache to expose the size of its items.
Additionally, we should emit prometheus metrics for total number of cached items which can help root cause issues that result in the VM operator pod running out of memory.
Please tell us about your environment.
N/A
The text was updated successfully, but these errors were encountered: