-
Notifications
You must be signed in to change notification settings - Fork 831
Tuning grafana client queries to have domain as a filter #6856
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
base: master
Are you sure you want to change the base?
Conversation
"editorMode": "code", | ||
"expr": "avg by(operation) (rate(cadence_client_errors[$__rate_interval]))", | ||
"editorMode": "builder", | ||
"expr": "avg by(operation) (rate(cadence_client_errors{domain!~\"$domain\"}[$__rate_interval]))", |
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.
"average for all other domains" (!~
) seems backwards?
"options": { | ||
"mode": "exclude", | ||
"names": [ | ||
"HistoryClientRespondDecisionTaskCompleted" |
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.
it's often worth excluding poll-responses since they generally don't have issues like this and they just retry. but an exclude by regex for respond(decision|activity)
is probably best in that case.
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.
Some small things worth verifying or changing (but feel free to skip the exclude one if you don't have a feel for that one yet), but merge when done 👍
Tuning the queries for client - adding domain filters for all prometheus queries
Why?
queries need to incorporate the filters from above
How did you test it?
locally
Potential risks
low