-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Use a globing operator in top-line metrics dashboard for the "all" value #4057
Conversation
Signed-off-by: Matt Miller <mamiller@rosettastone.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mmiller1, this works great! 👍
Before:
sum(irate(response_total{classification="success", deployment=~"emoji|linkerd-controller|linkerd-destination|linkerd-grafana|linkerd-identity|linkerd-prometheus|linkerd-proxy-injector|linkerd-sp-validator|linkerd-tap|linkerd-web|vote-bot|voting|web"}[30s])) / sum(irate(response_total{deployment=~"emoji|linkerd-controller|linkerd-destination|linkerd-grafana|linkerd-identity|linkerd-prometheus|linkerd-proxy-injector|linkerd-sp-validator|linkerd-tap|linkerd-web|vote-bot|voting|web"}[30s]))
After:
sum(irate(response_total{classification="success", deployment=~".*"}[30s])) / sum(irate(response_total{deployment=~".*"}[30s]))
Cool! Does this change correspond to what is documented here under Custom all value? Just want to better understand the context around this change. There are a number of other places that still use
|
Signed-off-by: Matt Miller <mamiller@rosettastone.com>
Yes, @ihcsim that is the documentation section that discusses what this changes, I don't see any reason why no to make the change to the other variables, so I added a commit to do so. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use a globing operator in top-line metrics dashboard for the "all" value
In clusters with many namespaces and deployments, the grafana query to prometheus for "all" may be too large for prometheus to return results.
Instead of having grafana query prometheus for every namespace/deployment literally, we can use a globing operator to shorten the request length so results can be returned in clusters where there are large numbers of deployments and namespaces.