Skip to content
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

Some graphs should be rates? #4

Open
larsks opened this issue Mar 4, 2020 · 2 comments
Open

Some graphs should be rates? #4

larsks opened this issue Mar 4, 2020 · 2 comments

Comments

@larsks
Copy link

larsks commented Mar 4, 2020

It looks like some queries in your dashboard should be using rate(). For example, the "Fetch data (SELECT)" chart uses:

pg_stat_database_tup_fetched{datname=~"$datname", instance=~"$instance"}

But pg_state_database_tup_fetched is a counter, and is generally charted via rate():

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.

@DaveOHenry
Copy link
Contributor

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"})

@spuyet
Copy link

spuyet commented May 20, 2024

Yeah definitely, multiple graph do not use the right queries/units.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants