docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

edits

This commit is contained in:
ddeyo 2018-09-07 10:46:05 -07:00
parent cd9541f1e9
commit 55d44b1498
1 changed files with 3 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
ee/ucp/admin/configure/collect-cluster-metrics.md
View File

@ -1,7 +1,7 @@
---
description: Collecting cluster metrics with Prometheus
description: Collecting UCP cluster metrics with Prometheus
keywords: prometheus, metrics
title: Collect cluster metrics with Prometheus
title: Collect UCP cluster metrics with Prometheus
redirect_from:
- /engine/admin/prometheus/
---
@ -15,12 +15,6 @@ 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
container, and monitor your Docker instance using Prometheus.
> **Warning**: The available metrics and the names of those metrics are in
> active development and may change at any time.
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.