关键词:
prometheus它是一个主动拉取的数据库,在K8S中应该展示图形的grafana数据实例化要保存下来,使用分布式文件系统加动态PV,但是在本测试环境中使用本地磁盘,安装采集数据的agent使用DaemonSet来部署,DaemonSet的特性就是在每个node上部署一个服务进程,这一切都是自动的部署。
此处只讲如何用prometheus来监控K8S集群,关于prometheus的知识参考官方文档。
部署前提: 准备好所需要的文件
$ ls -l Prometheus/prometheus#:/data/Prometheus/prometheus# ls -l total 28 drwxr-xr-x 2 root root 4096 Jan 15 02:53 grafana drwxr-xr-x 2 root root 4096 Jan 15 03:11 kube-state-metrics -rw-r--r-- 1 root root 60 Jan 14 06:48 namespace.yaml drwxr-xr-x 2 root root 4096 Jan 15 03:22 node-directory-size-metrics drwxr-xr-x 2 root root 4096 Jan 15 03:02 node-exporter drwxr-xr-x 2 root root 4096 Jan 15 02:55 prometheus drwxr-xr-x 2 root root 4096 Jan 15 02:37 rbac $ ls grafana/ grafana-configmap.yaml grafana-core-deployment.yaml grafana-import-dashboards-job.yaml grafana-pvc-claim.yaml grafana-pvc-volume.yaml grafana-service.yaml $ ls prometheus/ configmap.yaml deployment.yaml prometheus-rules.yaml service.yaml
grafana和 prometheus 都是部署文件,node-exporter、kube-state-metrics、node-directory-size-metrics这三个是采集器,相当于prometheus的agent
文件准备好了,现在开始一步一步来部署:
1,,创建所需Namespace
因为prometheus 部署的所有的deploy、pod、svc都是在monitoring完成的,所以需要事先创建之。
$ cat namespace.yaml apiVersion: v1 kind: Namespace metadata: name: monitoring $ kubectl create -f namespace.yaml namespace "monitoring" created
2,创建grafana的pv、 pvc
grafana# cat grafana-pvc-volume.yaml kind: PersistentVolume apiVersion: v1 metadata: name: grafana-pv-volume labels: type: local spec: storageClassName: grafana-pv-volume capacity: storage: 10Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Recycle hostPath: path: "/data/volume/grafana" grafana# cat grafana-pvc-claim.yaml kind: PersistentVolumeClaim apiVersion: v1 metadata: name: grafana-pvc-volume namespace: "monitoring" spec: accessModes: - ReadWriteOnce resources: requests: storage: 5Gi storageClassName: grafana-pv-volume $ kubectl create -f grafana/grafana-pvc-volume.yaml -f grafana/grafana-pvc-claim.yaml persistentvolume "grafana-pv-volume" created persistentvolumeclaim "grafana-pvc-volume" created $ kubectl get pvc -n monitoring NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE grafana-pvc-volume Bound grafana-pv-volume 10Gi RWO grafana-pv-volume 52s 状态bound已绑定到了 grafana-pv-volume
3,创建grafana应用,这些应用都是第三方的,都会有自已的配置,通过configmap来定义
grafana# ls grafana-configmap.yaml grafana-core-deployment.yaml grafana-import-dashboards-job.yaml grafana-pvc-claim.yaml grafana-pvc-volume.yaml grafana-service.yaml grafana# kubectl create -f ./ #grafana目录下所有文件都创建 configmap "grafana-import-dashboards" created deployment "grafana-core" created job "grafana-import-dashboards" created service "grafana" created grafana# kubectl get deployment,pod -n monitoring NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE deploy/grafana-core 1 1 1 0 1m NAME READY STATUS RESTARTS AGE po/grafana-core-9c7f66868-7q8lx 0/1 ContainerCreating 0 1m 运行po/grafana-core 容器时会下载镜像: grafana/grafana:4.2.0
grafana创建的应用 简单的自已描述了下:
grafana-pv-volume=/data/volume/grafana =10G grafana-pvc-volume=5G--->grafana-pv-volume ---configmap=grafana-import-dashboards Job=grafana-import-dashboards Deployment=grafana-core replicas: 1 containers=grafana-core mount: grafana-pvc-volume:/var service=grafana port: 3000 = nodePort: 30161 (3000是grafana服务的默认端口)
4, 现在grafana的核心应用已部署好了,现在来部署prometheus的RBAC
prometheus/rbac# ls grant_serviceAccount.sh prometheus_rbac.yaml #先创建RBAC文件: prometheus/rbac# kubectl create -f prometheus_rbac.yaml clusterrolebinding "prometheus-k8s" created clusterrolebinding "kube-state-metrics" created clusterrole "kube-state-metrics" created serviceaccount "kube-state-metrics" created clusterrolebinding "prometheus" created clusterrole "prometheus" created serviceaccount "prometheus-k8s" created prometheus/rbac#
5,创建prometheus的deloyment,service
prometheus/prometheus# ls configmap.yaml deployment.yaml prometheus-rules.yaml service.yaml prometheus/prometheus# 在configmap.yaml中要注意的是在1.7以后,获取cadvsion监控pod等的信息时,用的是kubelet的4194端口, 注意以下这段:这是采集cadvision信息,必须是通过kubelet的4194端口,所以Kubelet必须监听着,4194部署了cadvsion来获取pod中容器信息 prometheus/prometheus#cat configmap.yaml # https://github.com/prometheus/prometheus/blob/master/documentation/examples/prometheus-kubernetes.yml#L37 - job_name: 'kubernetes-nodes' tls_config: ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token kubernetes_sd_configs: - role: node relabel_configs: - source_labels: [__address__] regex: '(.*):10250' replacement: '${1}:10255' target_label: __address__ - job_name: 'kubernetes-cadvisor' scheme: https tls_config: ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token kubernetes_sd_configs: - role: node relabel_configs: - action: labelmap regex: __meta_kubernetes_node_label_(.+) - target_label: __address__ replacement: kubernetes.default.svc.cluster.local:443 - source_labels: [__meta_kubernetes_node_name] regex: (.+) target_label: __metrics_path__ replacement: /api/v1/nodes/${1}:4194/proxy/metrics # https://github.com/prometheus/prometheus/blob/master/documentation/examples/prometheus-kubernetes.yml#L79
prometheus-rules.yaml 这是它的发现规则文件
deployment.yaml service.yaml 这两个是部署的文件, deployment部署中资源限制建议放大一点
现在部署prometheus目录下所有文件:
prometheus/prometheus# kubectl create -f ./ configmap "prometheus-core" created deployment "prometheus-core" created configmap "prometheus-rules" created service "prometheus" created prometheus/prometheus# prometheus/prometheus# kubectl get deployment,pod -n monitoring NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE deploy/grafana-core 1 1 1 1 16m deploy/prometheus-core 1 1 1 1 1m NAME READY STATUS RESTARTS AGE po/grafana-core-9c7f66868-wm68j 1/1 Running 0 16m po/prometheus-core-6dc6777c5b-5nc7j 1/1 Running 0 1m
prometheus应用的部署,简单描述下创建的内容:
Deployment= prometheus-core replicas: 1 containers=prometheus image: prom/prometheus:v1.7.0 containerPort: 9090(webui) Service name: prometheus NodePort-->port: 9090 -webui
6,prometheus部署完了现在来部署它的agent,也就是采集器:
Prometheus/prometheus# ls node-directory-size-metrics/ daemonset.yaml Prometheus/prometheus# ls kube-state-metrics/ deployment.yaml service.yaml Prometheus/prometheus# ls node-exporter/ exporter-daemonset.yaml exporter-service.yaml Prometheus/prometheus# #其中两个用的是daemonset Prometheus/prometheus# kubectl create -f node-exporter/ -f kube-state-metrics/ -f node-directory-size-metrics/ daemonset "prometheus-node-exporter" created service "prometheus-node-exporter" created deployment "kube-state-metrics" created service "kube-state-metrics" created daemonset "node-directory-size-metrics" created Prometheus/prometheus# Prometheus/prometheus# kubectl get deploy,pod,svc -n monitoring NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE deploy/grafana-core 1 1 1 1 26m deploy/kube-state-metrics 2 2 2 2 1m deploy/prometheus-core 1 1 1 1 11m NAME READY STATUS RESTARTS AGE po/grafana-core-9c7f66868-wm68j 1/1 Running 0 26m po/kube-state-metrics-694fdcf55f-bqcp8 1/1 Running 0 1m po/kube-state-metrics-694fdcf55f-nnqqd 1/1 Running 0 1m po/node-directory-size-metrics-n9wx7 2/2 Running 0 1m po/node-directory-size-metrics-ppscw 2/2 Running 0 1m po/prometheus-core-6dc6777c5b-5nc7j 1/1 Running 0 11m po/prometheus-node-exporter-kchmb 1/1 Running 0 1m po/prometheus-node-exporter-lks5m 1/1 Running 0 1m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE svc/grafana NodePort 10.254.231.25 <none> 3000:30161/TCP 26m svc/kube-state-metrics ClusterIP 10.254.156.51 <none> 8080/TCP 1m svc/prometheus NodePort 10.254.239.90 <none> 9090:37318/TCP 10m svc/prometheus-node-exporter ClusterIP None <none> 9100/TCP 1m Prometheus/prometheus# -------- Prometheus/prometheus# kubectl get pod -o wide -n monitoring NAME READY STATUS RESTARTS AGE IP NODE prometheus-node-exporter-kchmb 1/1 Running 0 4m 10.3.1.16 10.3.1.16 prometheus-node-exporter-lks5m 1/1 Running 0 4m 10.3.1.17 10.3.1.17 #这两个是exporter,用的是daemonset 分别在这两个node上运行了。这样就可以采集到所有数据了。
如上部署完成,以下是用自已的话简单描述下:
node-exporter/exporter-daemonset.yaml 文件: DaemonSet=prometheus-node-exporter containers: name: prometheus-node-exporter image: prom/node-exporter:v0.14.0 containerPort: 9100 hostPort: 9100 hostNetwork: true #它用的是主机的9100端口 Prometheus/prometheus/node-exporter# kubectl get daemonset,pod -n monitoring NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE ds/node-directory-size-metrics 2 2 2 2 2 <none> 16h ds/prometheus-node-exporter 2 2 2 2 2 <none> 16h 因为它是daemonset,所以相应的也会运行着两个Pod: prometheus-node-exporter Service=prometheus-node-exporter clusterIP: None port: 9100 type: ClusterIP #它没有clusterIP # kubectl get service -n monitoring NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE prometheus-node-exporter ClusterIP None <none> 9100/TCP 16h
kube-state-metrics/deployment.yaml 文件: Deployment=kube-state-metrics replicas: 2 containers-->name: kube-state-metrics image: gcr.io/google_containers/kube-state-metrics:v0.5.0 containerPort: 8080 Service name: kube-state-metrics port: 8080 #没有映射 #kubectl get deployment,pod,svc -n monitoring NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE deploy/kube-state-metrics 2 2 2 2 16h NAME READY STATUS RESTARTS AGE po/kube-state-metrics-694fdcf55f-2mmd5 1/1 Running 0 11h po/kube-state-metrics-694fdcf55f-bqcp8 1/1 Running 0 16h NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE svc/kube-state-metrics ClusterIP 10.254.156.51 <none> 8080/TCP 16h
node-directory-size-metrics/daemonset.yaml 文件: #因为是daemonset,所以未定义replicas数量,直接运行在每个node之上,但是它没有创建service DaemonSet : name: node-directory-size-metrics containers-->name: read-du image: giantswarm/tiny-tools mountPath: /mnt/var mountPath: /tmp containers--> name: caddy image: dockermuenster/caddy:0.9.3 containerPort: 9102 mountPath: /var/www hostPath /var kubectl get daemonset,pod,svc -n monitoring NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE ds/node-directory-size-metrics 2 2 2 2 2 <none> 16h NAME READY STATUS RESTARTS AGE po/node-directory-size-metrics-n9wx7 2/2 Running 0 16h po/node-directory-size-metrics-ppscw 2/2 Running 0 16h NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE 没有node-directory-size-metrics的service
到此 prometheus算是部署完成了,最后来看下它暴露的端口:
Prometheus/prometheus# kubectl get svc -o wide -n monitoring NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR grafana NodePort 10.254.231.25 <none> 3000:30161/TCP 31m app=grafana,component=core kube-state-metrics ClusterIP 10.254.156.51 <none> 8080/TCP 6m app=kube-state-metrics prometheus NodePort 10.254.239.90 <none> 9090:37318/TCP 16m app=prometheus,component=core prometheus-node-exporter ClusterIP None <none> 9100/TCP 6m app=prometheus,component=node-exporter Prometheus/prometheus#
7,访问、使用prometheus
如上可以看到grafana的端口号是30161,NodeIP:30161 就可以打开grafana,默认admin/admin
登录后,添加数据源:
添加Prometheus的数据源:
将Prometheus的作为数据源的相关参数如下图所示:
添加完后,导入模板文件:
部署完成。
k8s的kafka监控(prometheus+grafana)
欢迎访问我的GitHub对于部署在K8S上的Kafka来说,Prometheus+Grafana是常用的监控方案,今天就来实战通过Prometheus+Grafana监控K8S环境的Kafka;准备工作今天聚焦的是Kafka监控,因此需要K8S、Helm、Kafka、Prometheus、Grafana等服务都已就绪,下... 查看详情
prometheus监控k8s(代码片段)
文章目录一、监控方案二、监控流程三、Kubernetes监控指标四、服务发现:五、使用Prometheus监控Kubernetes(1)部署前准备(2)采用daemonset方式部署node-exporter(3)部署Prometheus(4)部署grafana 查看详情
prometheus监控k8s(代码片段)
文章目录一、监控方案二、监控流程三、Kubernetes监控指标四、服务发现:五、使用Prometheus监控Kubernetes(1)部署前准备(2)采用daemonset方式部署node-exporter(3)部署Prometheus(4)部署grafana 查看详情
基于prometheus监控k8s集群
本文建立在你已经会安装prometheus服务的基础之上,如果你还不会安装,请参考:prometheus多维度监控容器如果你还没有安装库k8s集群,情参考: 从零开始搭建基于calico的kubenetes前言kubernetes显然已成为各大公司亲睐的容器编排... 查看详情
k8s结合prometheus构建企业级监控告警系统
深度解读Prometheus什么是Prometheus?Prometheus是一个开源的系统监控和报警系统,现在已经加入到CNCF基金会,成为继k8s之后第二个在CNCF托管的项目,在kubernetes容器管理系统中,通常会搭配prometheus进行监控,... 查看详情
k8s+prometheus+grafana的监控部署(代码片段)
...署k8s集群可以参考https://www.cnblogs.com/liugp/p/12115945.html二、Prometheus+Grafana的监控部署2.1、master/node节点环境部署在【master】可以进行安装部署安装git,并下载相关yaml文件https://gitee.com/liugpwwwroot/k8s-prometheus-grafana.git在【node】节点下... 查看详情
prometheus-operator结合grafana展示k8s监控
1.接上篇:kubernetes全面监控之prometheus-operator部署部署完成后,其实本身已经部署了grafana,也可以正常访问。但是我感觉太单调,数据不够详实。2.产生个想法,再多部署一套grafana,然后数据源使用prometheus-operator的数据源,再选... 查看详情
prometheus+grafana(代码片段)
一、Prometheus简介、容器监控的实现方对比虚拟机或者物理机来说比大的区别,比如容器在k8s环境中可以任意横向扩容与缩容,那么就需要监控服务能够自动对新创建的容器进行监控,当容器删除后又能够及时的从监控服务中删... 查看详情
使用 Prometheus 监控 CPU 利用率
】使用Prometheus监控CPU利用率【英文标题】:MonitoringCPUUtilizationusingPrometheus【发布时间】:2018-08-0116:14:38【问题描述】:我正在尝试监控安装和运行Prometheus的机器的CPU利用率。我有一个指标process_cpu_seconds_total。我可以找到这个指... 查看详情
搭建prometheus监控k8s服务(代码片段)
理论提示:在这里部署的prometheus,是使用的coreos提供的prometheus项目MetricsServer:是k8s集群资源使用情况的聚合器,收集数据给k8s集群内使用,如kubectl,hpa,scheduler等。PrometheusOperator:是一个系统检测和警报工具箱,... 查看详情
prometheus+grafan监控k8s集群详解(代码片段)
一,Prometheus概述1,什么是Prometheus?Prometheus是最初在SoundCloud上构建的开源系统监视和警报工具包,自2012年成立以来,许多公司和组织都采用了Prometheus,该项目拥有非常活跃的开发人员和用户社区。现在,它是一个独立的开源... 查看详情
prometheus监控k8s安装测试记录
...─node-exporter-service.yaml││└──node-exporter.yaml│└──prometheus组件4│├──configmap││├──config.yaml││├──config.yaml.bak││├──prometheus.yaml││├──rules- 查看详情
k8s部署prometheus和grafana监控pod和机器资源(11)
...化的界面,主要负责展示信息,功能非常强大,可以结合prometheus、zabbix、进行收集暂时,另外包括mysql,zk、etcd,nginx这些数据都可以收集展示prometheus是一个时序的数据库,什么是时序的数据库,就是对之前的数据进行存放,但... 查看详情
k8s/kubesphere监控部署实战图文流程部署nodeexporterprometheusgrafana(代码片段)
文章目录前言部署node-exporter部署Prometheus部署Grafana前言NodeExporter、Prometheus、Grafana都是监控领域的知名工具,它们各自具有不同的作用:NodeExporter是一个开源的Prometheusexporter,它是一个轻量级的代理程序,可以定... 查看详情
kube-prometheus监控k8s集群外服务的两种方式(代码片段)
方式一:通过ServiceMonitor方式创建Service和ServiceMonitor文件名为external-node.yaml---apiVersion:v1kind:Servicemetadata:name:external-node-exporternamespace:monitoringlabels:app:external-node-exporterapp.kubernetes. 查看详情
实战prometheus搭建监控系统(代码片段)
..."书",获取后台回复“k8s”,可领取k8s资料Prometheus是一款基于时序数据库的开源监控告警系统,说起Prometheus则不得不提SoundCloud,这是一个在线音乐分享的平台,类似于做视频分享的YouTube,由于他们... 查看详情
实战prometheus搭建监控系统(代码片段)
..."书",获取后台回复“k8s”,可领取k8s资料Prometheus是一款基于时序数据库的开源监控告警系统,说起Prometheus则不得不提SoundCloud,这是一个在线音乐分享的平台,类似于做视频分享的YouTube,由于他们... 查看详情
kubernetes第七篇:使用kubernetes部署prometheus+grafana监控系统(kubernetes工作实践类)
...录一、前言二、K8s监控系统架构2.1Prometheus简介2.2Prometheus架构2.3Prometheus知识普及三、K8s监控系统搭建3.1三类数据采集metrics3.2Prometheus+Grafana3.3实践一下... 查看详情