@@ -15,7 +15,7 @@ Deploy a Resource to Use with Prometheus
15
15
You can use the :ref:`mongodb-prometheus-sample.yaml
16
16
<mdb-prometheus-sample>` file to deploy a MongoDB resource in your
17
17
|k8s| cluster, with a :github:`ServiceMonitor
18
- </ prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides /getting-started.md#related-resources >`
18
+ <prometheus-operator/prometheus-operator/blob/main/Documentation/developer /getting-started.md>`
19
19
to indicate to Prometheus how to consume metrics data from
20
20
it.
21
21
@@ -84,7 +84,7 @@ Create a MongoDB Resource
84
84
You can use the :ref:`mongodb-prometheus-sample.yaml
85
85
<mdb-prometheus-sample>` file to deploy a MongoDB resource in your
86
86
|k8s| cluster, with a :github:`ServiceMonitor
87
- </ prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides /getting-started.md#related-resources >`
87
+ <prometheus-operator/prometheus-operator/blob/main/Documentation/developer /getting-started.md>`
88
88
to indicate to Prometheus how to consume metrics data from
89
89
it.
90
90
@@ -107,7 +107,7 @@ Prometheus endpoint. The command creates both |k8s-secrets| in the
107
107
``mongodb`` namespace.
108
108
109
109
This command also creates a :github:`ServiceMonitor
110
- </ prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides /getting-started.md#related-resources >` that
110
+ <prometheus-operator/prometheus-operator/blob/main/Documentation/developer /getting-started.md>` that
111
111
configures Prometheus to consume this resource's metrics. This command
112
112
creates the ``ServiceMonitor`` in the ``prometheus-system``
113
113
namespace.
@@ -163,14 +163,14 @@ The following response appears:
163
163
164
164
After a few minutes, the MongoDB resource should return to the
165
165
Running phase. Now you must configure the Prometheus
166
- :github:`ServiceMonitor </ prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides /getting-started.md#related-resources >`
166
+ :github:`ServiceMonitor <prometheus-operator/prometheus-operator/blob/main/Documentation/developer /getting-started.md>`
167
167
to point to the HTTPS endpoint.
168
168
169
169
Update ServiceMonitor
170
170
~~~~~~~~~~~~~~~~~~~~~
171
171
172
172
To update the :github:`ServiceMonitor
173
- </ prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides /getting-started.md#related-resources >`, run
173
+ <prometheus-operator/prometheus-operator/blob/main/Documentation/developer /getting-started.md>`, run
174
174
the following command to patch the resource again:
175
175
176
176
.. code-block:: sh
@@ -191,7 +191,7 @@ The following reponse appears:
191
191
servicemonitor.monitoring.coreos.com/mongodb-sm patched
192
192
193
193
With these changes, the new :github:`ServiceMonitor
194
- </ prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides /getting-started.md#related-resources >`
194
+ <prometheus-operator/prometheus-operator/blob/main/Documentation/developer /getting-started.md>`
195
195
points to the HTTPS endpoint (defined in
196
196
``/spec/endpoints/0/scheme``). You also set
197
197
``spec/endpoints/0/tlsConfig/insecureSkipVerify`` to ``true``,
@@ -208,7 +208,7 @@ using HTTPS.
208
208
209
209
Create the following ``mongodb-prometheus-sample.yaml`` file to deploy
210
210
a MongoDB resource in your |k8s| cluster, with a
211
- :github:`ServiceMonitor </ prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides /getting-started.md#related-resources >`
211
+ :github:`ServiceMonitor <prometheus-operator/prometheus-operator/blob/main/Documentation/developer /getting-started.md>`
212
212
to indicate to Prometheus how to consume metrics data from
213
213
it.
214
214
0 commit comments