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
We are seeing extension-agent constantly being throttled, which is not a problem in and of itself.
But this has the side effect that in a typical setup like ours using the kube-prometheus-stack and it's InfoInhibitor inhibition_rule it can cause noisy CPUThrottlingHigh alerts when there is another alert with "severity: warning" in the kube-system namespace.
Question
Since we don't have control over the settings like namespace and resources of the extension-agent, is there another recommended way of preventing the constantly firing CPUThrottlingHigh notifications from reaching our com channels?
The text was updated successfully, but these errors were encountered:
We are seeing extension-agent constantly being throttled, which is not a problem in and of itself.
But this has the side effect that in a typical setup like ours using the kube-prometheus-stack and it's InfoInhibitor inhibition_rule it can cause noisy CPUThrottlingHigh alerts when there is another alert with "severity: warning" in the kube-system namespace.
Question
Since we don't have control over the settings like namespace and resources of the extension-agent, is there another recommended way of preventing the constantly firing CPUThrottlingHigh notifications from reaching our com channels?
The text was updated successfully, but these errors were encountered: