We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It looks like some queries in your dashboard should be using rate(). For example, the "Fetch data (SELECT)" chart uses:
rate()
pg_stat_database_tup_fetched{datname=~"$datname", instance=~"$instance"}
But pg_state_database_tup_fetched is a counter, and is generally charted via rate():
pg_state_database_tup_fetched
rate(pg_stat_database_tup_fetched{datname=~"$datname", instance=~"$instance"}[5m])
It looks like the "Insert data", "Update data", and "Return data" charts (at least) have the same issue.
The text was updated successfully, but these errors were encountered:
The "Cache Hit Rate" panel has the same issue:
pg_stat_database_blks_hit{instance="$instance", datname=~"$datname"} / (pg_stat_database_blks_read{instance="$instance", datname=~"$datname"} + pg_stat_database_blks_hit{instance="$instance", datname=~"$datname"})
Sorry, something went wrong.
Yeah definitely, multiple graph do not use the right queries/units.
No branches or pull requests
It looks like some queries in your dashboard should be using
rate()
. For example, the "Fetch data (SELECT)" chart uses:But
pg_state_database_tup_fetched
is a counter, and is generally charted viarate()
:It looks like the "Insert data", "Update data", and "Return data" charts (at least) have the same issue.
The text was updated successfully, but these errors were encountered: