什么是普罗米修斯？

Prometheus是最初在SoundCloud上构建的开源系统监视和警报工具包。html

自2012年成立以来，许多公司和组织都采用了Prometheus，该项目拥有很是活跃的开发人员和用户社区。node

组件说明

MetricServer：是kubernetes集群资源使用状况的聚合器，收集数据给kubernetes集群内使用，如kubectl,hpa,scheduler等。
PrometheusOperator：是一个系统监测和警报工具箱，用来存储监控数据。
NodeExporter：用于各node的关键度量指标状态数据。
KubeStateMetrics：收集kubernetes集群内资源对象数据，制定告警规则。
Prometheus：采用pull方式收集apiserver，scheduler，controller-manager，kubelet组件数据，经过http协议传输。
Grafana：是可视化数据统计和监控平台。

系统架构

何时合适？

Prometheus很是适合记录任何纯数字时间序列。git

它既适合以机器为中心的监视，也适合于高度动态的面向服务的体系结构的监视。在微服务世界中，它对多维数据收集和查询的支持是一种特别的优点。github

Prometheus的设计旨在提升可靠性，使其成为中断期间要使用的系统，以使您可以快速诊断问题。api

每一个Prometheus服务器都是独立的，而不依赖于网络存储或其余远程服务。当基础结构的其余部分损坏时，您能够依靠它，而且无需设置普遍的基础结构便可使用它。服务器

何时不合适？

普罗米修斯重视可靠性。即便在故障状况下，您始终能够查看有关系统的可用统计信息。网络

若是您须要100％的准确性（例如按请求计费），则Prometheus并非一个不错的选择，由于所收集的数据可能不会足够详细和完整。架构

在这种状况下，最好使用其余系统来收集和分析数据以进行计费，并使用Prometheus进行其他的监视。app

部署安装

　　Github : https://github.com/coreos/kube-prometheuside

　　一、下载官方源码文件（默认镜像源来自quay.io）

　　wget -o kube-prometheus.tgz https://github.com/coreos/kube-prometheus/archive/v0.3.0.tar.gz

　固然，若是你的国外网不太友好，也能够下载本人百度云文件（已修改镜像源到aliyuncs）kube-prometheus.tgz（eb3m ）

　　二、解压并部署安装

　　tar -zxvf kube-prometheus.tgz && cd kube-prometheus-0.3.0/manifests

　　kubectl create -f setup

　　until kubectl get servicemonitors --all-namespaces ; do date; sleep 1; echo ""; done

　　kubectl create -f .

[root@k8s-32 manifests]# ls -R
.: alertmanager-alertmanager.yaml              kube-state-metrics-service.yaml                             prometheus-clusterRole.yaml alertmanager-secret.yaml                    node-exporter-clusterRoleBinding.yaml                       prometheus-operator-serviceMonitor.yaml alertmanager-serviceAccount.yaml            node-exporter-clusterRole.yaml                              prometheus-prometheus.yaml alertmanager-serviceMonitor.yaml            node-exporter-daemonset.yaml                                prometheus-roleBindingConfig.yaml alertmanager-service.yaml                   node-exporter-serviceAccount.yaml                           prometheus-roleBindingSpecificNamespaces.yaml grafana-dashboardDatasources.yaml           node-exporter-serviceMonitor.yaml                           prometheus-roleConfig.yaml grafana-dashboardDefinitions.yaml           node-exporter-service.yaml                                  prometheus-roleSpecificNamespaces.yaml grafana-dashboardSources.yaml               prometheus-adapter-apiService.yaml                          prometheus-rules.yaml grafana-deployment.yaml                     prometheus-adapter-clusterRoleAggregatedMetricsReader.yaml  prometheus-serviceAccount.yaml grafana-serviceAccount.yaml                 prometheus-adapter-clusterRoleBindingDelegator.yaml         prometheus-serviceMonitorApiserver.yaml grafana-serviceMonitor.yaml                 prometheus-adapter-clusterRoleBinding.yaml                  prometheus-serviceMonitorCoreDNS.yaml grafana-service.yaml                        prometheus-adapter-clusterRoleServerResources.yaml          prometheus-serviceMonitorKubeControllerManager.yaml kube-state-metrics-clusterRoleBinding.yaml  prometheus-adapter-clusterRole.yaml                         prometheus-serviceMonitorKubelet.yaml kube-state-metrics-clusterRole.yaml         prometheus-adapter-configMap.yaml                           prometheus-serviceMonitorKubeScheduler.yaml kube-state-metrics-deployment.yaml          prometheus-adapter-deployment.yaml                          prometheus-serviceMonitor.yaml kube-state-metrics-roleBinding.yaml         prometheus-adapter-roleBindingAuthReader.yaml               prometheus-service.yaml kube-state-metrics-role.yaml                prometheus-adapter-serviceAccount.yaml setup kube-state-metrics-serviceAccount.yaml      prometheus-adapter-service.yaml kube-state-metrics-serviceMonitor.yaml      prometheus-clusterRoleBinding.yaml ./setup: 0namespace-namespace.yaml                                       prometheus-operator-0prometheusruleCustomResourceDefinition.yaml  prometheus-operator-deployment.yaml prometheus-operator-0alertmanagerCustomResourceDefinition.yaml  prometheus-operator-0servicemonitorCustomResourceDefinition.yaml  prometheus-operator-serviceAccount.yaml prometheus-operator-0podmonitorCustomResourceDefinition.yaml    prometheus-operator-clusterRoleBinding.yaml                       prometheus-operator-service.yaml prometheus-operator-0prometheusCustomResourceDefinition.yaml    prometheus-operator-clusterRole.yaml

ls -R

[root@k8s-32 manifests]# kubectl create -f setup/.
namespace/monitoring created customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/prometheuses.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created clusterrole.rbac.authorization.k8s.io/prometheus-operator created clusterrolebinding.rbac.authorization.k8s.io/prometheus-operator created deployment.apps/prometheus-operator created service/prometheus-operator created serviceaccount/prometheus-operator created [root@k8s-32 manifests]# kubectl create -f .
alertmanager.monitoring.coreos.com/main created secret/alertmanager-main created service/alertmanager-main created serviceaccount/alertmanager-main created servicemonitor.monitoring.coreos.com/alertmanager created secret/grafana-datasources created configmap/grafana-dashboard-apiserver created configmap/grafana-dashboard-cluster-total created configmap/grafana-dashboard-controller-manager created configmap/grafana-dashboard-k8s-resources-cluster created configmap/grafana-dashboard-k8s-resources-namespace created configmap/grafana-dashboard-k8s-resources-node created configmap/grafana-dashboard-k8s-resources-pod created configmap/grafana-dashboard-k8s-resources-workload created configmap/grafana-dashboard-k8s-resources-workloads-namespace created configmap/grafana-dashboard-kubelet created configmap/grafana-dashboard-namespace-by-pod created configmap/grafana-dashboard-namespace-by-workload created configmap/grafana-dashboard-node-cluster-rsrc-use created configmap/grafana-dashboard-node-rsrc-use created configmap/grafana-dashboard-nodes created configmap/grafana-dashboard-persistentvolumesusage created configmap/grafana-dashboard-pod-total created configmap/grafana-dashboard-pods created configmap/grafana-dashboard-prometheus-remote-write created configmap/grafana-dashboard-prometheus created configmap/grafana-dashboard-proxy created configmap/grafana-dashboard-scheduler created configmap/grafana-dashboard-statefulset created configmap/grafana-dashboard-workload-total created configmap/grafana-dashboards created deployment.apps/grafana created service/grafana created serviceaccount/grafana created servicemonitor.monitoring.coreos.com/grafana created clusterrole.rbac.authorization.k8s.io/kube-state-metrics created clusterrolebinding.rbac.authorization.k8s.io/kube-state-metrics created deployment.apps/kube-state-metrics created role.rbac.authorization.k8s.io/kube-state-metrics created rolebinding.rbac.authorization.k8s.io/kube-state-metrics created service/kube-state-metrics created serviceaccount/kube-state-metrics created servicemonitor.monitoring.coreos.com/kube-state-metrics created clusterrole.rbac.authorization.k8s.io/node-exporter created clusterrolebinding.rbac.authorization.k8s.io/node-exporter created daemonset.apps/node-exporter created service/node-exporter created serviceaccount/node-exporter created servicemonitor.monitoring.coreos.com/node-exporter created apiservice.apiregistration.k8s.io/v1beta1.metrics.k8s.io created clusterrole.rbac.authorization.k8s.io/prometheus-adapter created clusterrole.rbac.authorization.k8s.io/system:aggregated-metrics-reader created clusterrolebinding.rbac.authorization.k8s.io/prometheus-adapter created clusterrolebinding.rbac.authorization.k8s.io/resource-metrics:system:auth-delegator created clusterrole.rbac.authorization.k8s.io/resource-metrics-server-resources created configmap/adapter-config created deployment.apps/prometheus-adapter created rolebinding.rbac.authorization.k8s.io/resource-metrics-auth-reader created service/prometheus-adapter created serviceaccount/prometheus-adapter created clusterrole.rbac.authorization.k8s.io/prometheus-k8s created clusterrolebinding.rbac.authorization.k8s.io/prometheus-k8s created servicemonitor.monitoring.coreos.com/prometheus-operator created prometheus.monitoring.coreos.com/k8s created rolebinding.rbac.authorization.k8s.io/prometheus-k8s-config created rolebinding.rbac.authorization.k8s.io/prometheus-k8s created rolebinding.rbac.authorization.k8s.io/prometheus-k8s created rolebinding.rbac.authorization.k8s.io/prometheus-k8s created role.rbac.authorization.k8s.io/prometheus-k8s-config created role.rbac.authorization.k8s.io/prometheus-k8s created role.rbac.authorization.k8s.io/prometheus-k8s created role.rbac.authorization.k8s.io/prometheus-k8s created prometheusrule.monitoring.coreos.com/prometheus-k8s-rules created service/prometheus-k8s created serviceaccount/prometheus-k8s created servicemonitor.monitoring.coreos.com/prometheus created servicemonitor.monitoring.coreos.com/kube-apiserver created servicemonitor.monitoring.coreos.com/coredns created servicemonitor.monitoring.coreos.com/kube-controller-manager created servicemonitor.monitoring.coreos.com/kube-scheduler created servicemonitor.monitoring.coreos.com/kubelet created

kubectl create -f .

　　三、等待部署完成

　kubectl get pod -n monitoring

NAME READY STATUS RESTARTS AGE alertmanager-main-0                    2/2     Running   0 65m alertmanager-main-1                    2/2     Running   0 65m alertmanager-main-2                    2/2     Running   0 65m grafana-7c54b4677d-btwfb               1/1     Running   0 65m kube-state-metrics-58b656b699-p8m29    3/3     Running   0 65m node-exporter-rc5mx                    2/2     Running   0 65m node-exporter-vdzkb                    2/2     Running   0 65m node-exporter-xzdw2                    2/2     Running   0 65m prometheus-adapter-7d6f96974c-76m4z    1/1     Running   0 65m prometheus-k8s-0                       3/3     Running   1 65m prometheus-k8s-1                       3/3     Running   1 65m prometheus-operator-5bd99d6457-89n7h   1/1     Running   0          66m

　　四、更改访问模式（ClusterIP => NodePort）

　　　　1）Prometheus

　　　　kubectl edit svc/prometheus-k8s -n monitoring

　　　　2）Alert Manager

　　　　kubectl edit svc/alertmanager-main -n monitoring

　　　　3）Grafana

　　　　kubectl edit svc/grafana -n monitoring

　　五、访问MasterIP:Port，其中Grafana默认用户名和密码都是admin

　　　　>>> 普罗米修斯功能强大，目前我也尚未彻底掌握，具体应用还须要你们本身深度学习。