Open mattdurham opened 3 months ago
what's this problem means?
With an extreme number of labels the CPU will skyrocket instead of using the relabel component internally that has a cache to handle this situation. In reviewing some issues we found that there were high CPU spikes whenever service monitor went to relabel that would have been addressed with using a cache.
This issue has not had any activity in the past 30 days, so the needs-attention
label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention
label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
Request
The kuberenetes monitors have relabel rules but do not use the caching in the relabel component which can create issues with CPU.
Use case
Reduce cpu