-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Description
Documentation
What version of Dgraph are you using?
Dgraph version : v2.0.0-beta1
Dgraph SHA-256 : 178663a98a3d59879a3d5c42928c89eb5f83afc2bfc0093272941e7a53515847
Commit SHA-1 : 6fac5d7c4
Commit timestamp : 2020-01-30 14:45:54 +1100
Branch : HEAD
Go version : go1.13.7
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
https://github.com/dgraph-io/dgraph/blob/master/wiki/content/deploy/index.md#metrics
All badger metrics are in
http://localhost:8080/debug/vars
This statement:
Dgraph exposes metrics via the /debug/vars endpoint in JSON format and the /debug/prometheus_metrics endpoint in Prometheus's text-based format.
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 to go_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
dgraph_alpha_health_status{method="",status="error"} 1
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
dgraph_alpha_health_status{method="",status="ok"} 1
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:
dgraph_active_mutations_total{method="n.proposeAndWait",status=""} -1000