-
Notifications
You must be signed in to change notification settings - Fork 597
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
Warning many-to-many matching not allowed #119
Comments
If this is just a warning that is printed within the first few minutes after restarting Prometheus, then this is expected and nothing to worry about. |
unfortunately the log is constant... |
Unique warning I get after start:
|
Seeing a similar regular warning after upgrade to prometheus-operator release
|
did you find some solution @faheem-cliqz ? |
We are seeing the exact issue in our cluster with the following recording rules provided by kubernetes-mixin (using kube-prometheus) Versions:
All of the above rules have the error:
Raw Log
|
I am also experiencing this error on some clusters. Has anyone found a way to pinpoint which pods are causing the error? Increasing the Prometheus log level to debug doesn't seem to help. |
fwiw, my issue was due to prometheus discovering redundant services in another namespace |
Any updates on this issue? |
I'm getting the same issue when deploy "kube-prometheus-stack" version 48.3.1 using Helm on Google Kubernetes Engine (GKE). |
I got this warning in prometheus version v2.3.2
i've change the expressions of
kube_pod_container_resource_requests_memory_bytes
,kube_pod_container_resource_requests_cpu_cores
andnode_num_cpu
addingignoring
insteadon
This is the code:
I know that the
ignoring
operator will remove the labels that is inside of brackets, but, the warning it's solved now, but i'm not sure that it's working, i'm trying to testing this alertsCan someone validate it to me?
The text was updated successfully, but these errors were encountered: