From 66d9f945192ed12b938506a9c4e8198f5d858e37 Mon Sep 17 00:00:00 2001 From: Daniel Mai Date: Fri, 14 Sep 2018 09:02:05 -0700 Subject: [PATCH] docs: Update Prometheus metrics config file. As of Prometheus 2.0, Prometheus metrics must be in the text-based format. Source: https://prometheus.io/docs/instrumenting/exposition_formats/ --- wiki/content/deploy/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/wiki/content/deploy/index.md b/wiki/content/deploy/index.md index 7cf045607de..1eb92c66b73 100644 --- a/wiki/content/deploy/index.md +++ b/wiki/content/deploy/index.md @@ -1332,11 +1332,11 @@ Dgraph server instances more evenly. stage. Increasing this increases memory consumption. ## Monitoring -Dgraph exposes metrics via `/debug/vars` endpoint in json format. Dgraph doesn't store the metrics and only exposes the value of the metrics at that instant. You can either poll this endpoint to get the data in your monitoring systems or install **[Prometheus](https://prometheus.io/docs/introduction/install/)**. Replace targets in the below config file with the ip of your Dgraph instances and run prometheus using the command `prometheus -config.file my_config.yaml`. +Dgraph exposes metrics via the `/debug/vars` endpoint in json format and the `/debug/prometheus_metrics` endpoint in Prometheus's text-based format. Dgraph doesn't store the metrics and only exposes the value of the metrics at that instant. You can either poll this endpoint to get the data in your monitoring systems or install **[Prometheus](https://prometheus.io/docs/introduction/install/)**. Replace targets in the below config file with the ip of your Dgraph instances and run prometheus using the command `prometheus -config.file my_config.yaml`. ```sh scrape_configs: - job_name: "dgraph" - metrics_path: "/debug/vars" + metrics_path: "/debug/prometheus_metrics" scrape_interval: "2s" static_configs: - targets: