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

worker node proc

This commit is contained in:
ddeyo 2018-09-07 11:05:00 -07:00
parent 55d44b1498
commit 02e2f02627
1 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,6 +1,6 @@
--- ---
description: Collecting UCP cluster metrics with Prometheus description: Collecting UCP cluster metrics with Prometheus
keywords: prometheus, metrics keywords: prometheus, metrics, ucp
title: Collect UCP cluster metrics with Prometheus title: Collect UCP cluster metrics with Prometheus
redirect_from: redirect_from:
- /engine/admin/prometheus/ - /engine/admin/prometheus/
@ -20,3 +20,24 @@ In UCP 3.0, Prometheus servers were standard containers. In UCP 3.1, Prometheus
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. 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.
> **Warning**: Upgrading UCP from 3.0.x to 3.1.x causes loss of metrics data. > **Warning**: Upgrading UCP from 3.0.x to 3.1.x causes loss of metrics data.
## Deploy Prometheus on worker nodes
To deploy Prometheus on worker nodes in a cluster:
1. Begin by sourcing an admin bundle.
2. Verify that ucp-metrics pods are running on all managers.
```
$ kubectl -n kube-system get pods -l k8s-app=ucp-metrics -o wide
NAME READY STATUS RESTARTS AGE IP NODE
ucp-metrics-hvkr7 3/3 Running 0 4h 192.168.80.66 3a724a-0
```
3. Add a Kubernetes node label to one or more workers. Here we add a label with key "ucp-metrics" and value "".
```
$ kubectl label node 3a724a-1 ucp-metrics=
node "noah-3a724a-1" labeled
```