doc/cephadm: update custom j2 config-key name

introduced by:
cd79c9912ab35ee6296d613edc7830410a141e05

Signed-off-by: Michael Fritch <mfritch@suse.com>
(cherry picked from commit b58b0de77710fd511d30b79a9cc8f32b19ff29b0)

diff --git a/doc/cephadm/monitoring.rst b/doc/cephadm/monitoring.rst
index 92bf886e78631c6ae080c93534e48bcc6b063d22..2941894c195e6eaff3477f5e26ed476bdda75971 100644 (file)
--- a/doc/cephadm/monitoring.rst
+++ b/doc/cephadm/monitoring.rst
@@ -211,10 +211,10 @@ The following templates for files that will be generated by cephadm can be
 overridden. These are the names to be used when storing with ``ceph config-key
 set``:
 
-- ``alertmanager_alertmanager.yml``
-- ``grafana_ceph-dashboard.yml``
-- ``grafana_grafana.ini``
-- ``prometheus_prometheus.yml``
+- ``services/alertmanager/alertmanager.yml``
+- ``services/grafana/ceph-dashboard.yml``
+- ``services/grafana/grafana.ini``
+- ``services/prometheus/prometheus.yml``
 
 You can look up the file templates that are currently used by cephadm in
 ``src/pybind/mgr/cephadm/templates``:
@@ -254,7 +254,7 @@ Example
 .. code-block:: bash
 
   # set the contents of ./prometheus.yml.j2 as template
-  ceph config-key set mgr/cephadm/services_prometheus_prometheus.yml \
+  ceph config-key set mgr/cephadm/services/prometheus/prometheus.yml \
     -i $PWD/prometheus.yml.j2
 
   # restart cephadm mgr module