-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Docs: Missing Prometheus metrics or wrong metrics name or removed. (Grafana related) #4772
Comments
Goroutines total is |
Please consider adding the following metrics.
Alphas uptime Network I/O Disk I/O Utilization Dgraph Version (e.g we have go_info) A RAM metric usage specific for Zero
Maybe add a |
@MichelDiz most of those metrics can be obtained from other exporters. I too would like clarity on the |
Some of the mentioned issues had been resolved in #4948. |
Fixes #4772 This adds the following badger metrics into /debug/prometheus_metrics: badger_v2_disk_reads_total badger_v2_disk_writes_total badger_v2_gets_total badger_v2_lsm_bloom_hits_total (per level) badger_v2_lsm_level_gets_total (per level) badger_v2_memtable_gets_total badger_v2_puts_total badger_v2_read_bytes badger_v2_written_bytes This is added via the Prometheus expvar collector. Update metrics_test.go for the seven initial Badger versions (excluding the LSM metrics). This adds to the exposed Prometheus metrics. These metrics were already accessible via /debug/vars. The LSM metrics don't show up immediately. They show up after there are hits/gets to the LSM tree. Changes * Add Badger metrics to Prometheus * Update metrics test to check for badger metrics. Co-authored-by: Ibrahim Jarif <[email protected]>
Fixes #4772 This adds the following badger metrics into /debug/prometheus_metrics: badger_v2_disk_reads_total badger_v2_disk_writes_total badger_v2_gets_total badger_v2_lsm_bloom_hits_total (per level) badger_v2_lsm_level_gets_total (per level) badger_v2_memtable_gets_total badger_v2_puts_total badger_v2_read_bytes badger_v2_written_bytes This is added via the Prometheus expvar collector. Update metrics_test.go for the seven initial Badger versions (excluding the LSM metrics). This adds to the exposed Prometheus metrics. These metrics were already accessible via /debug/vars. The LSM metrics don't show up immediately. They show up after there are hits/gets to the LSM tree. Changes * Add Badger metrics to Prometheus * Update metrics test to check for badger metrics. Co-authored-by: Ibrahim Jarif <[email protected]>
Fixes #4772 This adds the following badger metrics into /debug/prometheus_metrics: badger_v2_disk_reads_total badger_v2_disk_writes_total badger_v2_gets_total badger_v2_lsm_bloom_hits_total (per level) badger_v2_lsm_level_gets_total (per level) badger_v2_memtable_gets_total badger_v2_puts_total badger_v2_read_bytes badger_v2_written_bytes This is added via the Prometheus expvar collector. Update metrics_test.go for the seven initial Badger versions (excluding the LSM metrics). This adds to the exposed Prometheus metrics. These metrics were already accessible via /debug/vars. The LSM metrics don't show up immediately. They show up after there are hits/gets to the LSM tree. Changes * Add Badger metrics to Prometheus * Update metrics test to check for badger metrics. Co-authored-by: Ibrahim Jarif <[email protected]>
Fixes dgraph-io#4772 This adds the following badger metrics into /debug/prometheus_metrics: badger_v2_disk_reads_total badger_v2_disk_writes_total badger_v2_gets_total badger_v2_lsm_bloom_hits_total (per level) badger_v2_lsm_level_gets_total (per level) badger_v2_memtable_gets_total badger_v2_puts_total badger_v2_read_bytes badger_v2_written_bytes This is added via the Prometheus expvar collector. Update metrics_test.go for the seven initial Badger versions (excluding the LSM metrics). This adds to the exposed Prometheus metrics. These metrics were already accessible via /debug/vars. The LSM metrics don't show up immediately. They show up after there are hits/gets to the LSM tree. Changes * Add Badger metrics to Prometheus * Update metrics test to check for badger metrics. Co-authored-by: Ibrahim Jarif <[email protected]>
Documentation
What version of Dgraph are you using?
Steps to reproduce the issue (command/config used to run Dgraph).
Check docs and compare with the endpoints:
http://localhost:6080/debug/prometheus_metrics
http://localhost:8080/debug/prometheus_metrics
Docs source
All badger metrics are in
http://localhost:8080/debug/vars
This statement:
Makes users (and me) think that it is part of Prometheus metrics. Which it can't be, cuz
/debug/vars
is a JSON response. So, my logical thinking says that it should be in/debug/prometheus_metrics
which also it isn't.What doesn't exists but it is in docs
dgraph_goroutines_total
(maybe it was changed togo_goroutines
?)Update
One thing that confuses me, and certainly would confuses users is that the metric
dgraph_alpha_health_status
appear in the Zero metrics but it has a different code
But, the Alphas has no errors at all, but it is giving this status and a positive number (which means false by logic).
In Alpha says
Following the Grafana logic, both are false. Following the status logic, "has error = 1/false" and "has status ok = 1/false".
Why?
Also, some metrics have negative numbers. Which doesn't make sense. Why I would have -1k of pending proposals? or -100 go_threads? These things can't have negative params.
e.g:
The text was updated successfully, but these errors were encountered: