@@ -249,6 +249,48 @@ assignments.
249
249
250
250
.. include:: /includes/setting-fileConf-mms.publicApi.whitelistEnabled.rst
251
251
252
+ Prometheus
253
+ ----------
254
+
255
+ You must configure the following settings to enable the metrics that are
256
+ available for ingestion through Prometheus. You can also configure these
257
+ settings in the :guilabel:`Custom` tab of the :ref:`Ops Manager Config
258
+ <admin-console-general-om-config>` page in the
259
+ :ref:`admin-console-general-tab`.
260
+
261
+ After configuring these settings, you must restart |mms| on each
262
+ instance. After restarting, the new Prometheus endpoint can be
263
+ accessed at a |url| in the following format:
264
+
265
+ .. code-block:: shell
266
+
267
+ http(s)://<opsManagerUri>:<port>/metrics
268
+
269
+ .. note::
270
+
271
+ You can designate a listening port for the Prometheus metrics. This
272
+ doesn't have to be the default port that |mms| uses, 8080 for |http| or
273
+ 8443 for |https|. Ensure that your network allows traffic to the
274
+ specified Prometheus metrics port.
275
+
276
+ After enabling, you must configure a new scrape config similar to the
277
+ following in Prometheus for each |onprem| server that you would like to
278
+ gather statistics from.
279
+
280
+ .. code-block:: shell
281
+ :caption: scrape_config
282
+
283
+ scrape_configs:
284
+
285
+ - job_name: 'opsmanager'
286
+ static_configs:
287
+ - targets: [<opsManagerHostname>:<port>]
288
+
289
+ Note that each server's endpoint only provides metrics for the same server.
290
+
291
+ .. include:: /includes/setting-fileConf-mms.prom.listening.enabled.rst
292
+ .. include:: /includes/setting-fileConf-mms.prom.listening.port.rst
293
+
252
294
Push Live Migrations
253
295
--------------------
254
296
0 commit comments