PMM-监控MongoDB

本是古典何须时尚 2024-02-18 17:57 67阅读 0赞

### 1. Percona监控和管理概述 ###

Percona监控和管理（PMM）是一个用于管理和监控MySQL和MongoDB性能的开源平台。 它由Percona与托管数据库服务，支持和咨询领域的专家合作开发。 PMM是一个免费的开源解决方案，您可以在自己的环境中运行，以实现最大的安全性和可靠性。 它为mysql和mongodb服务器提供全面的基于时间的分析，以确保您的数据尽可能高效地工作。

#### 1.1 Percona监控和管理架构 ####

PMM平台基于简单的客户端 – 服务器模型，可实现高效的可扩展性。它包括以下模块：  
PMM Client安装在您要监视的每个数据库主机上。它收集服务器指标，一般系统指标和查询分析数据，以获得完整的性能概述。收集的数据发送到PMM服务器。  
PMM Server是PMM的核心部分，它聚合收集的数据，并以Web界面的表格，仪表板和图形的形式呈现。  
PMM是旨在无缝协同工作的工具集合。一些是由Percona开发的，一些是第三方开源工具。  
下图说明了PMM当前的结构：  
![1500277349772.png_resize_535_2C472][]

#### 1.2 PMM Client ####

PMM客户端软件包适用于大多数流行的Linux发行版：  
– Red Hat Enterprise linux衍生产品的RPM（包括CentOS，Oracle Linux，Amazon Linux等）  
– DEB用于基于Debian的发行版（包括Ubuntu等）

PMM客户端软件包包含以下内容：  
pmm-admin是用于管理PMM客户端的命令行工具，例如，添加和删除要监视的数据库实例。  
percona-qan-agent是一种在收集查询性能数据时管理查询分析（QAN）代理的服务。它还与PMM服务器中的QAN API连接，并发送收集的数据。  
node\_exporter是收集一般系统指标的Prometheus exporter。有关详细信息，请参阅[https://github.com/prometheus/node\_exporter][https_github.com_prometheus_node_exporter]。  
mysqld\_exporter是收集MySQL服务器指标的Prometheus exporter。有关详细信息，请参阅[https://github.com/percona/mysqld\_exporter][https_github.com_percona_mysqld_exporter]。  
mongodb\_exporter是收集MongoDB服务器指标的Prometheus exporter。有关详细信息，请参阅[https://github.com/percona/mongodb\_exporter][https_github.com_percona_mongodb_exporter]。  
proxysql\_exporter是收集ProxySQL性能指标的Prometheus exporter。有关详细信息，请参阅[https://github.com/percona/proxysql\_exporter][https_github.com_percona_proxysql_exporter]。

#### 1.3 PMM Server ####

PMM服务器将作为您的中央监控主机的机器运行。它通过以下方式作为设备分发：  
可以用于运行容器的Docker映像  
可以在VirtualBox或其他管理程序中运行  
可以通过Amazon Web Services（AWS）运行的Amazon Machine Image（AMI）  
PMM服务器由以下工具组成：  
查询分析（QAN）使您能够在一段时间内分析MySQL查询性能。除客户端QAN代理外，还包括以下内容：

QAN API是用于存储和访问在PMM客户端上运行的percona-qan-agent收集的查询数据的后端  
QAN Web App是用于可视化收集的Query Analytics数据的Web应用程序。  
度量监视器（MM）提供对MySQL或MongoDB服务器实例至关重要的度量的历史视图。它包括以下内容：

Prometheus是一个第三方时间序列数据库，连接到在PMM客户端上运行的出口商，并汇总了收集的指标.  
Consul提供一个PMM客户端可以远程列出，添加和删除Prometheus主机的API。  
Grafana是一个第三方仪表板和图形构建器，用于在直观的Web界面中可视化由Prometheus汇总的数据.  
Percona仪表板是由Percona开发的Grafana仪表板  
Orchestrator是MySQL复制拓扑管理和可视化工具。  
部署方案(https://www.percona.com/doc/percona-monitoring-and-management/architecture.html\#id13)

参考：  
\[1\] [ https://prometheus.io/docs/introduction/overview/][https_prometheus.io_docs_introduction_overview]  
\[2\] [https://www.consul.io/docs/][https_www.consul.io_docs]  
\[3\] [http://docs.grafana.org/][http_docs.grafana.org]  
\[4\] [ https://github.com/outbrain/orchestrator/wiki/Orchestrator-Manual][https_github.com_outbrain_orchestrator_wiki_Orchestrator-Manual]

### 2. 安装MongoDB ###

#### 2.1 配置Percona yum源 ####

安装命令如下：

sudo yum install http://www.percona.com/downloads/percona-release/redhat/0.1-4/percona-release-0.1-4.noarch.rpm

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 <div style="height:15px"> 
 
 </div> 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 sudo 
 yum 
 install 
 http 
 : 
 //www.percona.com/downloads/percona-release/redhat/0.1-4/percona-release-0.1-4.noarch.rpm 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

请确保有安装成功结果：

Installed: percona-release.noarch 0:0.1-4 Complete!

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 Installed 
 : 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 percona 
 - 
 release 
 . 
 noarch 
 
 0 
 : 
 0.1 
 - 
 4 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 Complete 
 ! 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

sudo yum list | grep percona

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 <div style="height:15px">
 1 
 </div> 
 <div style="height:15px">
 2 
 </div> 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 sudo 
 yum 
 list 
 
 | 
 
 grep 
 percona 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

显示部分的安装包：

percona-release.noarch 0.1-4 installed Percona-SQL-50-debuginfo.x86\_64 5.0.92-b23.89.rhel6 percona-release-x86\_64 Percona-SQL-client-50.x86\_64 5.0.92-b23.89.rhel6 percona-release-x86\_64 Percona-SQL-devel-50.x86\_64 5.0.92-b23.89.rhel6 percona-release-x86\_64 Percona-SQL-server-50.x86\_64 5.0.92-b23.89.rhel6 percona-release-x86\_64 Percona-SQL-shared-50.x86\_64 5.0.92-b23.89.rhel6 percona-release-x86\_64 Percona-SQL-shared-compat.x86\_64 5.0.92-b23.89.rhel6 percona-release-x86\_64 Percona-SQL-test-50.x86\_64 5.0.92-b23.89.rhel6 percona-release-x86\_64 Percona-Server-51-debuginfo.x86\_64 5.1.73-rel14.12.624.rhel6 percona-release-x86\_64 Percona-Server-55-debuginfo.x86\_64 5.5.55-rel38.8.el6 percona-release-x86\_64 Percona-Server-56-debuginfo.x86\_64 5.6.36-rel82.0.el6 percona-release-x86\_64 Percona-Server-57-debuginfo.x86\_64 5.7.18-15.1.el6 percona-release-x86\_64 Percona-Server-MongoDB.x86\_64 3.0.15-1.10.el6 percona-release-x86\_64 Percona-Server-MongoDB-32.x86\_64 3.2.13-3.3.el6 percona-release-x86\_64 3.2.13-3.3.el6 percona-release-x86\_64 3.2.13-3.3.el6 percona-release-x86\_64 3.2.13-3.3.el6 percona-release-x86\_64 3.2.13-3.3.el6 percona-release-x86\_64 3.2.13-3.3.el6 percona-release-x86\_64 Percona-Server-MongoDB-34.x86\_64 3.4.5-1.5.el6 percona-release-x86\_64

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 percona 
 - 
 release 
 . 
 noarch 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 0.1 
 - 
 4 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 installed&nbsp;&nbsp; 
 </div> 
 <div> 
 Percona 
 - 
 SQL 
 - 
 50 
 - 
 debuginfo 
 . 
 x86 
 _64 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 5.0.92 
 - 
 b23 
 . 
 89.rhel6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 SQL 
 - 
 client 
 - 
 50.x86_64 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 5.0.92 
 - 
 b23 
 . 
 89.rhel6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 SQL 
 - 
 devel 
 - 
 50.x86_64 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 5.0.92 
 - 
 b23 
 . 
 89.rhel6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 SQL 
 - 
 server 
 - 
 50.x86_64 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 5.0.92 
 - 
 b23 
 . 
 89.rhel6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 SQL 
 - 
 shared 
 - 
 50.x86_64 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 5.0.92 
 - 
 b23 
 . 
 89.rhel6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 SQL 
 - 
 shared 
 - 
 compat 
 . 
 x86 
 _64 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 5.0.92 
 - 
 b23 
 . 
 89.rhel6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 SQL 
 - 
 test 
 - 
 50.x86_64 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 5.0.92 
 - 
 b23 
 . 
 89.rhel6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 Server 
 - 
 51 
 - 
 debuginfo 
 . 
 x86 
 _64 
 &nbsp;&nbsp;&nbsp;&nbsp; 
 5.1.73 
 - 
 rel14 
 . 
 12.624.rhel6 
 &nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 Server 
 - 
 55 
 - 
 debuginfo 
 . 
 x86 
 _64 
 &nbsp;&nbsp;&nbsp;&nbsp; 
 5.5.55 
 - 
 rel38 
 . 
 8.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 Server 
 - 
 56 
 - 
 debuginfo 
 . 
 x86 
 _64 
 &nbsp;&nbsp;&nbsp;&nbsp; 
 5.6.36 
 - 
 rel82 
 . 
 0.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 Server 
 - 
 57 
 - 
 debuginfo 
 . 
 x86 
 _64 
 &nbsp;&nbsp;&nbsp;&nbsp; 
 5.7.18 
 - 
 15.1.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 Server 
 - 
 MongoDB 
 . 
 x86 
 _64 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 3.0.15 
 - 
 1.10.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 Server 
 - 
 MongoDB 
 - 
 32.x86_64 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 3.2.13 
 - 
 3.3.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86 
 _64 
 </div> 
 <div> 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 3.2.13 
 - 
 3.3.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86 
 _64 
 </div> 
 <div> 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 3.2.13 
 - 
 3.3.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86 
 _64 
 </div> 
 <div> 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 3.2.13 
 - 
 3.3.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86 
 _64 
 </div> 
 <div> 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 3.2.13 
 - 
 3.3.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86 
 _64 
 </div> 
 <div> 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 3.2.13 
 - 
 3.3.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86_64 
 </div> 
 <div> 
 Percona 
 - 
 Server 
 - 
 MongoDB 
 - 
 34.x86_64 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 3.4.5 
 - 
 1.5.el6 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 percona 
 - 
 release 
 - 
 x86 
 _64 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

这里我们安装MongoDB3.4版本

sudo yum install Percona-Server-MongoDB-34

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 sudo 
 yum 
 install 
 Percona 
 - 
 Server 
 - 
 MongoDB 
 - 
 34 
 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

**如果您已经启用SELinux，则需要做配置相关，这里不做详细说明。我是禁用SELinux状态。**

MongoDB默认配置文件`/etc/mongod.conf`，数据目录默认是`/var/lib/mongodb/` 。有需要，请自行修改配置文件。

查看MongoDB是否启动：

/etc/init.d/mongod status

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 / 
 etc 
 / 
 init 
 . 
 d 
 / 
 mongod 
 status 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

### 3. 部署Percona监控和管理 ###

以下过程介绍如何正确部署PMM：  
在主机上运行PMM Server，用于访问收集的数据，查看基于时间的图表，并执行性能分析。

以下安装的选项可用：  
\* 使用Docker运行PMM服务器  
\* 使用VirtualBox运行PMM服务器  
\* 使用Amazon Machine Image（AMI）运行PMM服务器

这里我们选择使用Docker运行PMM服务器。

使用docker运行PMM Server  
PMM服务器的Docker映像公开托管在https://hub.docker.com/r/percona/pmm-server/。 如果要从docker映像运行PMM Server，则主机必须能够运行Docker 1.12.6或更高版本，并具有网络访问权限。 有关使用Docker的更多信息，请参阅[Docker文档][Docker]。

#### 3.1 yum安装Docker ####

一般CentOS需要安装`epel`源，我这里是aws ec2 linux，所以直接使用如下命令安装：

yum install docker service docker start chkconfig docker on

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 yum 
 install 
 docker 
 </div> 
 <div> 
 service 
 docker 
 start 
 </div> 
 <div> 
 chkconfig 
 docker 
 on 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

> 注意：  
> 使用pmm-server映像时，请使用特定的版本标签，而不是最新的标签。目前的最新稳定版本是1.2.0。

#### 3.2 创建一个PMM数据容器 ####

要创建持久PMM数据的容器，请运行以下命令：

docker create \\ -v /opt/prometheus/data \\ -v /opt/consul-data \\ -v /var/lib/mysql \\ -v /var/lib/grafana \\ --name pmm-data \\ percona/pmm-server:1.2.0 /bin/true

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 docker 
 create 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 - 
 v 
 
 / 
 opt 
 / 
 prometheus 
 / 
 data 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 - 
 v 
 
 / 
 opt 
 / 
 consul 
 - 
 data 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 - 
 v 
 
 / 
 var 
 / 
 lib 
 / 
 mysql 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 - 
 v 
 
 / 
 var 
 / 
 lib 
 / 
 grafana 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 -- 
 name 
 pmm 
 - 
 data 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 percona 
 / 
 pmm 
 - 
 server 
 : 
 1.2.0 
 
 / 
 bin 
 / 
 true 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

运行结果：

Unable to find image 'percona/pmm-server:1.2.0' locally 1.2.0: Pulling from percona/pmm-server 45a2e645736c: Pull complete fe1f1770c826: Pull complete 4f1bdb417453: Pull complete a2f3207fd166: Pull complete 2f8fffdaf5ef: Pull complete 46e8ca929fde: Pull complete 5c89a1a51b6b: Pull complete fceac4be9a77: Pull complete fb79d7de9adf: Pull complete Digest: sha256:b9e200c9bc66bb2c31d75d57852474cf00a292d3ccb8301fdd55cc6e25738e3d Status: Downloaded newer image for percona/pmm-server:1.2.0 a93b2e74a10afe3b47e127e7ef43072cff8e9b060c2a0e1cbdf7a0baae8dd712

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 Unabletofindimage'percona/pmm-server:1.2.0'locally 
 </div> 
 <div> 
 1.2.0 
 : 
 
 Pulling 
 from 
 percona 
 / 
 pmm 
 - 
 server 
 </div> 
 <div> 
 45a2e645736c 
 : 
 
 Pull 
 complete 
 </div> 
 <div> 
 fe1f1770c826 
 : 
 
 Pull 
 complete 
 
 </div> 
 <div> 
 4f1bdb417453 
 : 
 
 Pull 
 complete 
 </div> 
 <div> 
 a2f3207fd166 
 : 
 
 Pull 
 complete 
 
 </div> 
 <div> 
 2f8fffdaf5ef 
 : 
 
 Pull 
 complete 
 
 </div> 
 <div> 
 46e8ca929fde 
 : 
 
 Pull 
 complete 
 
 </div> 
 <div> 
 5c89a1a51b6b 
 : 
 
 Pull 
 complete 
 </div> 
 <div> 
 fceac4be9a77 
 : 
 
 Pull 
 complete 
 </div> 
 <div> 
 fb79d7de9adf 
 : 
 
 Pull 
 complete 
 </div> 
 <div> 
 Digest 
 : 
 
 sha256 
 : 
 b9e200c9bc66bb2c31d75d57852474cf00a292d3ccb8301fdd55cc6e25738e3d 
 </div> 
 <div> 
 Status 
 : 
 
 Downloaded 
 newer 
 image 
 for 
 
 percona 
 / 
 pmm 
 - 
 server 
 : 
 1.2.0 
 </div> 
 <div> 
 a93b2e74a10afe3b47e127e7ef43072cff8e9b060c2a0e1cbdf7a0baae8dd712 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

> 注意：  
> 这个容器不运行，它只是为了确保在升级到更新的PMM – server映像时保留所有PMM数据。不要删除或重新创建这个容器，除非您打算删除所有PMM数据并从头开始。

前面的命令解释：  
`docker create`命令表示docker守护进程从镜像中创建容器。  
`- v`选项对`volumes`进行指定初始化 。  
`--name`选项为容器指定一个自定义名称，用于在Docker网络中引用容器。例如名字：`pmm-server`。  
`percona/pmm-server:1.2.0`是自源的镜像的名字和版本标识。  
`/bin/true`容器进行运行的命令。

#### 3.3 创建并运行PMM服务器容器 ####

要运行PMM服务器，请使用以下命令：

docker run -d \\ -p 80:80 \\ --volumes-from pmm-data \\ --name pmm-server \\ --restart always \\ percona/pmm-server:1.2.0

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 docker 
 run 
 
 - 
 d 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 - 
 p 
 
 80 
 : 
 80 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 -- 
 volumes 
 - 
 from 
 pmm 
 - 
 data 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 -- 
 name 
 pmm 
 - 
 server 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 -- 
 restart 
 always 
 
 \ 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 percona 
 / 
 pmm 
 - 
 server 
 : 
 1.2.0 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

e8e133c3af3669257debdbce89bd36080510b2b2be30b0595cf295eb891f7d42

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 e8e133c3af3669257debdbce89bd36080510b2b2be30b0595cf295eb891f7d42 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

前面的命令解释：  
`docker run`命令运行一个docker守护进程以运行容器。  
`- d`选项以分离模式(即在后台)启动容器。  
`- p`选项用于映射访问PMM服务器web UI的端口。如果端口80不可用，您可以使用`- p 8080:80`将登录页面映射到端口8080。  
`--volumes-from`表示挂载容器来自前面步骤指定的`pmm-data`。  
`--name`选项为容器指定一个自定义名称，用于在Docker网络中引用容器。例如名字：`pmm-server`。  
`--restart`选项定义容器的重新启动策略。设置它始终确保Docker守护进程在启动时启动容器，如果容器退出，则重新启动它。  
`percona/pmm-server:1.2.0`是自源的镜像的名字和版本标识。

使用如下命令确认PMM 安装运行是否正确：

netstat -tpln|grep 80

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 netstat 
 
 - 
 tpln 
 | 
 grep 
 
 80 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

通过使用运行容器的主机的IP地址连接到PMM Web界面来验证PMM服务器是否正在运行，然后在要监视的所有数据库主机上安装PMM Client  
Component URL  
PMM landing page http://172.31.27.176:80  
Query Analytics (QAN web app) http://172.31.27.176/qan/  
Metrics Monitor (Grafana) http://172.31.27.176/graph/User name: admin Password: admin  
Orchestrator http://172.31.27.176/orchestrator

#### 3.4 安装PMM客户端 ####

PMM客户端是安装在您要监视的MySQL或MongoDB主机的客户端和数据提供采集方。 组件收集关于一般系统和数据库性能的各种数据，并将该数据发送到相应的PMM服务器组件。

> 注意：  
> 不应该在具有相同主机名的数据库服务器上安装代理，因为PMM服务器使用主机名来标识收集的数据。

安装PMM客户端

安装pmm-client软件包

sudo yum install pmm-client -y

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 sudo 
 yum 
 install 
 pmm 
 - 
 client 
 
 - 
 y 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

将PMM客户端连接到PMM服务器

使用`pmm-admin config --help`，查看帮助

`pmm-admin config --server 172.31.27.176:80`

OK, PMM server is alive. PMM Server | 172.31.27.176:80 Client Name | ip-172-31-27-176 Client Address | 172.17.0.1

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 OK 
 , 
 
 PMM 
 server 
 is 
 
 alive 
 . 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 PMM 
 Server 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 172.31.27.176 
 : 
 80 
 
 </div> 
 <div> 
 Client 
 Name 
 &nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 ip 
 - 
 172 
 - 
 31 
 - 
 27 
 - 
 176 
 </div> 
 <div> 
 Client 
 Address 
 &nbsp;&nbsp; 
 | 
 
 172.17.0.1 
 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

#### 3.5 pmm server与pmm client通信 ####

从以下操作也可以看出，pmm并不支持代理，是C/S构架。

`pmm-admin check-network`检查结果：

PMM Network Status Server Address | 172.31.27.176:80 ient Address | 172.17.0.1 \* System Time NTP Server (0.pool.ntp.org) | 2017-07-17 07:55:57 +0000 UTC PMM Server | 2017-07-17 07:55:57 +0000 GMT PMM Client | 2017-07-17 07:55:57 +0000 UTC PMM Server Time Drift | OK PMM Client Time Drift | OK PMM Client to PMM Server Time Drift | OK \* Connection: Client --> Server -------------------- ------- SERVER SERVICE STATUS -------------------- ------- Consul API OK Prometheus API OK Query Analytics API OK Connection duration | 75.404µs Request duration | 625.358µs Full round trip | 700.762µs \* Connection: Client <-- Server ---------------- ----------------- ----------------- ------- ---------- --------- SERVICE TYPE NAME REMOTE ENDPOINT STATUS HTTPS/TLS PASSWORD ---------------- ----------------- ----------------- ------- ---------- --------- linux:metrics ip-172-31-27-176 172.17.0.1:42000 DOWN YES - mongodb:metrics ip-172-31-27-176 172.17.0.1:42003 DOWN YES - When an endpoint is down it may indicate that the corresponding service is stopped (run 'pmm-admin list' to verify). If it's running, check out the logs /var/log/pmm-\*.log When all endpoints are down but 'pmm-admin list' shows they are up and no errors in the logs, check the firewall settings whether this system allows incoming connections from server to address:port in question. Also you can check the endpoint status by the URL: http://172.31.27.176:80/prometheus/targets

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 PMM 
 Network 
 Status 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 Server 
 Address 
 
 | 
 
 172.31.27.176 
 : 
 80 
 </div> 
 <div> 
 &nbsp;&nbsp; 
 ient 
 Address 
 
 | 
 
 172.17.0.1 
 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 * 
 
 System 
 Time 
 </div> 
 <div> 
 NTP 
 Server 
 
 ( 
 0.pool.ntp.org 
 ) 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 2017 
 - 
 07 
 - 
 17 
 
 07 
 : 
 55 
 : 
 57 
 
 + 
 0000 
 
 UTC 
 </div> 
 <div> 
 PMM 
 Server 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 2017 
 - 
 07 
 - 
 17 
 
 07 
 : 
 55 
 : 
 57 
 
 + 
 0000 
 
 GMT 
 </div> 
 <div> 
 PMM 
 Client 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 2017 
 - 
 07 
 - 
 17 
 
 07 
 : 
 55 
 : 
 57 
 
 + 
 0000 
 
 UTC 
 </div> 
 <div> 
 PMM 
 Server 
 Time 
 Drift 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 OK 
 </div> 
 <div> 
 PMM 
 Client 
 Time 
 Drift 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 OK 
 </div> 
 <div> 
 PMM 
 Client 
 to 
 
 PMM 
 Server 
 Time 
 Drift 
 
 | 
 
 OK 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 * 
 
 Connection 
 : 
 
 Client 
 
 -- 
 &gt; 
 
 Server 
 </div> 
 <div> 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 - 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 </div> 
 <div> 
 SERVER 
 SERVICE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 STATUS 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 </div> 
 <div> 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 - 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 </div> 
 <div> 
 Consul 
 API&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 OK 
 </div> 
 <div> 
 Prometheus 
 API&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 OK 
 </div> 
 <div> 
 Query 
 Analytics 
 API&nbsp;&nbsp; 
 OK 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 Connection 
 duration 
 
 | 
 
 75.404µ 
 s 
 </div> 
 <div> 
 Request 
 duration 
 &nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 625.358µ 
 s 
 </div> 
 <div> 
 Full 
 round 
 trip 
 &nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 700.762µ 
 s 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 * 
 
 Connection 
 : 
 
 Client 
 
 &lt; 
 -- 
 
 Server 
 </div> 
 <div> 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 -- 
 - 
 </div> 
 <div> 
 SERVICE 
 TYPE&nbsp;&nbsp;&nbsp;&nbsp; 
 NAME&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 REMOTE 
 ENDPOINT&nbsp;&nbsp; 
 STATUS&nbsp;&nbsp; 
 HTTPS 
 / 
 TLS&nbsp;&nbsp; 
 PASSWORD 
 
 </div> 
 <div> 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 -- 
 - 
 </div> 
 <div> 
 linux 
 : 
 metrics&nbsp;&nbsp;&nbsp;&nbsp; 
 ip 
 - 
 172 
 - 
 31 
 - 
 27 
 - 
 176 
 &nbsp;&nbsp; 
 172.17.0.1 
 : 
 42000 
 &nbsp;&nbsp; 
 DOWN&nbsp;&nbsp;&nbsp;&nbsp; 
 YES 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 - 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 </div> 
 <div> 
 mongodb 
 : 
 metrics&nbsp;&nbsp; 
 ip 
 - 
 172 
 - 
 31 
 - 
 27 
 - 
 176 
 &nbsp;&nbsp; 
 172.17.0.1 
 : 
 42003 
 &nbsp;&nbsp; 
 DOWN&nbsp;&nbsp;&nbsp;&nbsp; 
 YES 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 - 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 When 
 an 
 endpoint 
 is 
 
 down 
 it 
 may 
 indicate 
 that 
 the 
 corresponding 
 service 
 is 
 
 stopped 
 
 ( 
 run 
 
 'pmm-admin list' 
 
 to 
 
 verify 
 ) 
 . 
 </div> 
 <div> 
 If 
 
 it 
 's running, check out the logs /var/log/pmm-*.log 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 When all endpoints are down but ' 
 pmm 
 - 
 admin 
 list' 
 
 shows 
 they 
 are 
 up 
 and 
 
 no 
 errors 
 in 
 
 the 
 logs 
 , 
 </div> 
 <div> 
 check 
 the 
 firewall 
 settings 
 whether 
 this 
 
 system 
 allows 
 incoming 
 connections 
 from 
 server 
 to 
 
 address 
 : 
 port 
 in 
 
 question 
 . 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 Also 
 you 
 can 
 check 
 the 
 endpoint 
 status 
 by 
 the 
 URL 
 : 
 
 http 
 : 
 //172.31.27.176:80/prometheus/targets 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

防火墙开启与docker容器通信：

iptables -A INPUT -s 172.0.0.1/8 -j ACCEPT service iptables save

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 iptables 
 
 - 
 A 
 
 INPUT 
 
 - 
 s 
 
 172.0.0.1 
 / 
 8 
 
 - 
 j 
 
 ACCEPT 
 </div> 
 <div> 
 service 
 iptables 
 save 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

`pmm-admin check-network`再次查看结果，则通信正常。

PMM Network Status Server Address | 172.31.27.176:80 Client Address | 172.17.0.1 \* System Time NTP Server (0.pool.ntp.org) | 2017-07-17 07:56:40 +0000 UTC PMM Server | 2017-07-17 07:56:40 +0000 GMT PMM Client | 2017-07-17 07:56:40 +0000 UTC PMM Server Time Drift | OK PMM Client Time Drift | OK PMM Client to PMM Server Time Drift | OK \* Connection: Client --> Server -------------------- ------- SERVER SERVICE STATUS -------------------- ------- Consul API OK Prometheus API OK Query Analytics API OK Connection duration | 67.174µs Request duration | 595.339µs Full round trip | 662.513µs \* Connection: Client <-- Server ---------------- ----------------- ----------------- ------- ---------- --------- SERVICE TYPE NAME REMOTE ENDPOINT STATUS HTTPS/TLS PASSWORD ---------------- ----------------- ----------------- ------- ---------- --------- linux:metrics ip-172-31-27-176 172.17.0.1:42000 OK YES - mongodb:metrics ip-172-31-27-176 172.17.0.1:42003 OK YES -

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 PMM 
 Network 
 Status 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 Server 
 Address 
 
 | 
 
 172.31.27.176 
 : 
 80 
 </div> 
 <div> 
 Client 
 Address 
 
 | 
 
 172.17.0.1 
 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 * 
 
 System 
 Time 
 </div> 
 <div> 
 NTP 
 Server 
 
 ( 
 0.pool.ntp.org 
 ) 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 2017 
 - 
 07 
 - 
 17 
 
 07 
 : 
 56 
 : 
 40 
 
 + 
 0000 
 
 UTC 
 </div> 
 <div> 
 PMM 
 Server 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 2017 
 - 
 07 
 - 
 17 
 
 07 
 : 
 56 
 : 
 40 
 
 + 
 0000 
 
 GMT 
 </div> 
 <div> 
 PMM 
 Client 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 2017 
 - 
 07 
 - 
 17 
 
 07 
 : 
 56 
 : 
 40 
 
 + 
 0000 
 
 UTC 
 </div> 
 <div> 
 PMM 
 Server 
 Time 
 Drift 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 OK 
 </div> 
 <div> 
 PMM 
 Client 
 Time 
 Drift 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 OK 
 </div> 
 <div> 
 PMM 
 Client 
 to 
 
 PMM 
 Server 
 Time 
 Drift 
 
 | 
 
 OK 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 * 
 
 Connection 
 : 
 
 Client 
 
 -- 
 &gt; 
 
 Server 
 </div> 
 <div> 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 - 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 </div> 
 <div> 
 SERVER 
 SERVICE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 STATUS 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 </div> 
 <div> 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 - 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 </div> 
 <div> 
 Consul 
 API&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 OK 
 </div> 
 <div> 
 Prometheus 
 API&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 OK 
 </div> 
 <div> 
 Query 
 Analytics 
 API&nbsp;&nbsp; 
 OK 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 Connection 
 duration 
 
 | 
 
 67.174µ 
 s 
 </div> 
 <div> 
 Request 
 duration 
 &nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 595.339µ 
 s 
 </div> 
 <div> 
 Full 
 round 
 trip 
 &nbsp;&nbsp;&nbsp;&nbsp; 
 | 
 
 662.513µ 
 s 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div>
 &nbsp; 
 </div> 
 <div> 
 * 
 
 Connection 
 : 
 
 Client 
 
 &lt; 
 -- 
 
 Server 
 </div> 
 <div> 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 -- 
 - 
 </div> 
 <div> 
 SERVICE 
 TYPE&nbsp;&nbsp;&nbsp;&nbsp; 
 NAME&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 REMOTE 
 ENDPOINT&nbsp;&nbsp; 
 STATUS&nbsp;&nbsp; 
 HTTPS 
 / 
 TLS&nbsp;&nbsp; 
 PASSWORD 
 
 </div> 
 <div> 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 - 
 
 -- 
 -- 
 -- 
 -- 
 -- 
 
 -- 
 -- 
 -- 
 -- 
 - 
 </div> 
 <div> 
 linux 
 : 
 metrics&nbsp;&nbsp;&nbsp;&nbsp; 
 ip 
 - 
 172 
 - 
 31 
 - 
 27 
 - 
 176 
 &nbsp;&nbsp; 
 172.17.0.1 
 : 
 42000 
 &nbsp;&nbsp; 
 OK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 YES 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 - 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 </div> 
 <div> 
 mongodb 
 : 
 metrics&nbsp;&nbsp; 
 ip 
 - 
 172 
 - 
 31 
 - 
 27 
 - 
 176 
 &nbsp;&nbsp; 
 172.17.0.1 
 : 
 42003 
 &nbsp;&nbsp; 
 OK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 YES 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 - 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

#### 3.6 pmm client添加监控项 ####

pmm-admin add linux:metrics \# 监控linux系统 pmm-admin add mongodb:metrics \# 监控mongodb pmm-admin add mongodb:queries --dev-enable \# 此处为实验功能，所以需要加 --dev-enable pmm-admin purge linux:metrics \# 清除数据 pmm-admin purge mongodb:metrics

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 pmm 
 - 
 admin 
 add 
 linux 
 : 
 metrics 
 &nbsp;&nbsp; 
 # 监控linux系统 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 add 
 mongodb 
 : 
 metrics 
 &nbsp;&nbsp; 
 # 监控mongodb 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 add 
 mongodb 
 : 
 queries 
 
 -- 
 dev 
 - 
 enable 
 &nbsp;&nbsp; 
 # 此处为实验功能，所以需要加 --dev-enable 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 purge 
 linux 
 : 
 metrics 
 &nbsp;&nbsp; 
 # 清除数据 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 purge 
 mongodb 
 : 
 metrics 
 &nbsp;&nbsp; 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

管理PMM客户端的一些命令说明：

\# 添加监控服务 pmm-admin add \# 检查PMM客户端和PMM服务器之间的网络连接。 pmm-admin check-network \# 配置PMM Client如何与PMM服务器通信。 pmm-admin config \# 打印任何命令和退出的帮助 pmm-admin help \# 打印有关PMM客户端的信息 pmm-admin info \# 列出此PMM客户端添加的所有监控服务 pmm-admin list \# 检查PMM服务器是否存活 pmm-admin ping \# 在PMM服务器上清除度量数据。 pmm-admin purge \# 清除监控服务 pmm-admin remove \# 修复安装 pmm-admin repair \# 重启pmm客户端 pmm-admin restart \# 打印PMM Client使用的密码 pmm-admin show-passwords \# 开启监控服务 pmm-admin start \# 停止监控服务 pmm-admin stop \# 在卸载之前清理PMM Client pmm-admin uninstall

<table style=""> 
 <tbody> 
 <tr> 
 <td> 
 <div style="font-size:12px!important; line-height:15px!important"> 
 
 </div> </td> 
 <td> 
 <div style=""> 
 <div> 
 # 添加监控服务 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 add 
 </div> 
 <div> 
 # 检查PMM客户端和PMM服务器之间的网络连接。 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 check 
 - 
 network 
 </div> 
 <div> 
 # 配置PMM Client如何与PMM服务器通信。 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 config 
 </div> 
 <div> 
 # 打印任何命令和退出的帮助 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 help 
 </div> 
 <div> 
 # 打印有关PMM客户端的信息 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 info 
 </div> 
 <div> 
 # 列出此PMM客户端添加的所有监控服务 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 list 
 </div> 
 <div> 
 # 检查PMM服务器是否存活 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 ping 
 </div> 
 <div> 
 # 在PMM服务器上清除度量数据。 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 purge 
 </div> 
 <div> 
 # 清除监控服务 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 remove 
 </div> 
 <div> 
 # 修复安装 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 repair 
 </div> 
 <div> 
 # 重启pmm客户端 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 restart 
 </div> 
 <div> 
 # 打印PMM Client使用的密码 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 show 
 - 
 passwords 
 </div> 
 <div> 
 # 开启监控服务 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 start 
 </div> 
 <div> 
 # 停止监控服务 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 stop 
 </div> 
 <div> 
 # 在卸载之前清理PMM Client 
 </div> 
 <div> 
 pmm 
 - 
 admin 
 uninstall 
 </div> 
 <div>
 &nbsp; 
 </div> 
 </div> </td> 
 </tr> 
 </tbody> 
</table>

#### 3.7 一些效果图 ####

![SouthEast][]![SouthEast 1][]![SouthEast 2][]

[1500277349772.png_resize_535_2C472]: https://i1.wp.com/www.linuxba.com/wp-content/uploads/2017/07/1500277349772.png?resize=535%2C472
[https_github.com_prometheus_node_exporter]: https://github.com/prometheus/node_exporter
[https_github.com_percona_mysqld_exporter]: https://github.com/percona/mysqld_exporter
[https_github.com_percona_mongodb_exporter]: https://github.com/percona/mongodb_exporter
[https_github.com_percona_proxysql_exporter]: https://github.com/percona/proxysql_exporter
[https_prometheus.io_docs_introduction_overview]: https://prometheus.io/docs/introduction/overview/
[https_www.consul.io_docs]: https://www.consul.io/docs/
[http_docs.grafana.org]: http://docs.grafana.org/
[https_github.com_outbrain_orchestrator_wiki_Orchestrator-Manual]: https://github.com/outbrain/orchestrator/wiki/Orchestrator-Manual
[Docker]: https://docs.docker.com/
[SouthEast]: https://img-blog.csdn.net/20180202164547231?watermark/2/text/aHR0cDovL2Jsb2cuY3Nkbi5uZXQvZWFnbGU4OQ==/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA==/dissolve/70/gravity/SouthEast
[SouthEast 1]: https://img-blog.csdn.net/20180202164527959?watermark/2/text/aHR0cDovL2Jsb2cuY3Nkbi5uZXQvZWFnbGU4OQ==/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA==/dissolve/70/gravity/SouthEast
[SouthEast 2]: https://image.dandelioncloud.cn/pgy_files/images/2024/01/29/cbdda7ea89bc4111a9ee901b6da1a48c.png