From 2d5142f2528ff6afef66bfe11f2f20afc64a7f18 Mon Sep 17 00:00:00 2001 From: ddeyo Date: Fri, 7 Sep 2018 10:38:20 -0700 Subject: [PATCH] restore topic to original state --- config/thirdparty/prometheus.md | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/config/thirdparty/prometheus.md b/config/thirdparty/prometheus.md index 736835f2a9..3560709a50 100644 --- a/config/thirdparty/prometheus.md +++ b/config/thirdparty/prometheus.md @@ -7,10 +7,6 @@ redirect_from: - /config/thirdparty/prometheus/ --- -> Beta disclaimer -> -> This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice. - [Prometheus](https://prometheus.io/) is an open-source systems monitoring and alerting toolkit. You can configure Docker as a Prometheus target. This topic shows you how to configure Docker, set up Prometheus to run as a Docker @@ -22,12 +18,6 @@ container, and monitor your Docker instance using Prometheus. Currently, you can only monitor Docker itself. You cannot currently monitor your application using the Docker target. -In UCP 3.0, Prometheus servers were standard containers. In UCP 3.1, Prometheus runs as a Kubernetes deployment. By default, this will be a daemonset that runs on every manager node. One benefit of this change is you can set the daemonset to not schedule on any nodes, which effectively disables Prometheus if you don’t use the UCP web interface. - -The data is stored locally on disk for each Prometheus server, so data is not replicated on new managers or if you schedule Prometheus to run on a new node. Metrics are not kept longer than 24 hours. - -> **Note:** Upgrading UCP from 3.0.x to 3.1.x causes loss of metrics data. - ## Configure Docker @@ -61,7 +51,7 @@ Docker now exposes Prometheus-compatible metrics on port 9323. ## Configure and run Prometheus -In this example, Prometheus runs as a Kubernetes deployment. +Prometheus runs as a Docker service on a Docker swarm. > **Prerequisites** >