Giter Club home page Giter Club logo

misc-grafana-dashboards's Introduction

Misc Grafana Dashboards

Misc collection of grafana dashboards used to visualize Prometheus metrics for Kubernetes Cluster

Dashboards

Docker Registry Dashboard

Image of Docker Registry dashboard

Links: Grafana.com | JSON

ChartMuseum Dashboard

Image of ChartMuseum dashboard

Links: Grafana.com | JSON

PostgreSQL Database Dashboard

Image of PostgreSQL Database dashboard 1 Image of PostgreSQL Database dashboard 2

Links: Grafana.com | JSON

misc-grafana-dashboards's People

Contributors

daveohenry avatar lstn avatar patsevanton avatar tylerpachal avatar uow-dmurrell avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

misc-grafana-dashboards's Issues

why tuple == byte?

Why for metrics where rows are selected, do you use the dimension in bytes?

eg
pg_stat_database_tup_fetched
Realino says nothing about the instance, if we treat each line as a byte.

Wrong unit for pg_stat_database_tup

The panels "Insert data", "Return data", "Fetch data", "Current fetch data" are all using a "size" unit which is wrong as pg_stat_database_tup_* metrics return number of rows...

Some graphs should be rates?

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.

Cluster monitor

I use one postgres_exporter for several databases, I see duplicate labels in the dashboard, how is it easier to implement an additional filter?

Usage questions

Hi, I couldn't add a "Question" label - but that's the intent of this issue:

  1. This dashboard uses postgress-exporter, does it need to be installed on the same machine where my Postgres database is? Or will it work if installed on a different machine and just provide the DB connection details?

I'm asking that mainly for the CPU & Memory usage metrics.. For some reason I see my DB has very low RAM usage, seems wayyy too low IMO (FYI, I installed PG using docker on a k8s pod and postgres-exporter on another pod using docker).
Screen Shot 2022-01-22 at 21 25 39

  1. How can I understand the metrics around CPU time? Usually, you see CPU usage as a percentage, but here it's CPU time. How can one tell if it's low/mid/high? Maybe you can help transfer it to percentage instead of CPU time?

  2. Does it report also the storage of the DB? Meaning how much storage the DB is using. And even better, how much storage it has left on the machine..

  3. I see also the "Start Time" is always NA for me.

Screen Shot 2022-01-22 at 21 29 16

Is that a problem on my end? Or in the dashboard?

  1. More of a pg-exporter question, but any special instructions on how to create the readonly user so everything will work? I did it this way: https://github.com/prometheus-community/postgres_exporter#running-as-non-superuser

Did I miss anything?

Thank you very much!

Postgre dashboard shows too many instances

When many pods that expose metrics are deployed it is quite a mess to find the correct one.
I think it has to do with the "Instance" variable in the dashboard. The query filters for all instances that have an "up" metric as far as I can tell. Unfortunately there can be many instances that have a metric with this name.
Is it possible to just use "pg_up" instead of "up"?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.