-
Notifications
You must be signed in to change notification settings - Fork 94
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
PromQL queries fail, but MQL works #325
Comments
Can you please email me your project ID so we can investigate further? (my GH user name) at (the company I work for) .com. |
Done |
Closing - there's a hard 100 labels-per-metric limit that is unlikely to be hit, except in a case like this where there's 50+ label keys and every one of them changes, while keeping the metric name the same. Deleting the metric descriptor fixed the problem. |
@lyanco could you please elaborate on this fix? Where and how do I delete the metric descriptor? I'm running into the exact same issue, same metric even. I count 57 labels on |
There's an API for it. I wrote some throwaway python code to do it. |
Thanks for the pointer! For anyone else that ends up here, here's my throwaway code and relabel config:
|
2 updates here: We recently increased the limit to 360 labels across all projects with the metric defined, so this should be less of an issue going forward. Here's a short go script we've been sending folks who have run into this issue that iterates through metrics, looks for a regex match on having more than 8 digits in a row (an indication of a common situation where someone sends statsd metrics by accident, which can have a timestamp in the metric name), and deletes them. Please feel free to use if needed:
|
As a workaround for #223, I set up self-deployed collection running in my single node kubeadm cluster so I could scape the kubelet cadvisor, with a config like:
At first I thought the metrics weren't getting ingested, because I could not query
container_cpu_usage_seconds_total
with my self-deployed prometheus frontend, nor the Managed Service for Prometheus page. I gotEmpty query result
, although the UIs would both auto-complete the metrics when I typed into the UI. This implied to me that they somehow knew about the metric, but I couldn't query them.When I tried the Cloud Monitoring Metrics Explorer, I was able to see the metrics. I'm not sure if it's something about this metric, or the # of labelsets (53), or what, but AFAICT MQL works to query it, but PromQL returns an empty query.
The text was updated successfully, but these errors were encountered: