From 12ae0f20c625dce253fceb76ff784320651f4e38 Mon Sep 17 00:00:00 2001
From: bermaker <495571751@qq.com>
Date: Sat, 7 Nov 2020 02:34:33 +0800
Subject: [PATCH] [Metrics] Fix prometheus configuration doc (#11856)

---
 doc/source/ray-metrics.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/source/ray-metrics.rst b/doc/source/ray-metrics.rst
index cac3308cf..3eec73516 100644
--- a/doc/source/ray-metrics.rst
+++ b/doc/source/ray-metrics.rst
@@ -37,11 +37,11 @@ Let's modify Prometheus's config file to scrape metrics from Prometheus endpoint
 
     # prometheus.yml
     global:
-    scrape_interval:     5s
-    evaluation_interval: 5s
+      scrape_interval:     5s
+      evaluation_interval: 5s
 
     scrape_configs:
-    - job_name: prometheus
+      - job_name: prometheus
         static_configs:
         - targets: ['localhost:8080'] # This must be same as metrics_export_port
 
@@ -159,4 +159,4 @@ Ray supports custom metrics APIs to enable developers to have visibility to thei
 
 It current supports 3 metric types. All metric types have the same definition as `Prometheus metric types <https://prometheus.io/docs/concepts/metric_types/>`_.
 
-:ref:`Custom Metrics APIs Package Reference <custom-metric-api-ref>`
\ No newline at end of file
+:ref:`Custom Metrics APIs Package Reference <custom-metric-api-ref>`