【kubernetes搭建（三）】搭建Promethus+grafana监控平台

已于 2022-11-11 09:44:03 修改
阅读量4.4k 收藏 8
点赞数 2
分类专栏： kubernetes 文章标签： kubernetes 容器
于 2021-10-25 09:12:02 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/sumengnan/article/details/120945199
版权

一、介绍

1、Prometheus(中文名:普罗米修斯)

是由SoundCloud开发的开源监控报警系统和时序列数据库(TSDB). Prometheus使用Go语言开发, 是Google BorgMon监控系统的开源版本。

Prometheus的基本原理是通过HTTP协议周期性抓取被监控组件的状态, 任意组件只要提供对应的HTTP接口就可以接入监控. 不需要任何SDK或者其他的集成过程。输出被监控组件信息的HTTP接口被叫做exporter，目前开发常用的组件大部分都有exporter可以直接使用, 比如Nginx、MySQL、Linux系统信息、Mongo、ES等

2、exporter

可以理解为一个数据库+数据抓取工具, 工具从各处抓来统一的数据, 放入prometheus这一个时间序列数据库中. 那如何保证各处的数据格式是统一的呢?就是通过这个exporter. Exporter是一类数据采集组件的总称. Exporter负责从目标处搜集数据, 并将其转化为Prometheus支持的格式, 它开放了一个http接口(以便Prometheus来抓取数据). 与传统的数据采集组件不同的是, Exporter并不向中央服务器发送数据, 而是等待中央服务器(如Prometheus等)主动前来抓取。https://github.com/prometheus 有很多写好的exporter,可以直接下载使用。

3、Grafana

是一个图形化工具, 它可以从很多种数据源(例如Prometheus)中读取数据信息, 使用很漂亮的图表来展示数据, 并且有很多开源的dashborad可以使用,可以快速地搭建起一个非常精美的监控平台。它与Prometheus的关系就类似于Kibana与ElasticSearch。

二、安装nfs（用于共享存储）

（最好单独用一个服务器用于共享存储服务器，类似于ftp）

1、NFS服务器：

yum install nfs-utils rpcbind -y
systemctl start rpcbind
systemctl enable rpcbind
systemctl start nfs
systemctl enable nfs
或
systemctl enable nfs-server
systemctl start nfs-server

mkdir -p /nfs/prometheus/data
mkdir -p /nfs/grafana/data
echo "/nfs/prometheus/data  192.168.16.0/24(rw,no_root_squash,sync,insecure)" >>/etc/exports
echo "/nfs/grafana/data  192.168.16.0/24(rw,no_root_squash,sync,insecure)" >>/etc/exports

#测试一下连接
showmount -e 49.233.42.34

（最后的命令重要，否则会报错The PersistentVolume "prometheus-data-pv" is invalid: spec.persistentvolumesource: Forbidden）

注意： 192.168.16.0/24网段，根据自己的ip addr结果去设置，否则下面Promethus和grafana连不上

修改后/etc/exports文件后，需要重启nfs

systemctl restart nfs
systemctl restart rpcbind

2、其他NFS客户端（k8s节点）：

如果是其他k8s节点直接启动rpcbind并且挂载目录就可以

yum install nfs-utils rpcbind -y
#如果没安装nfs-utils，挂载时会报错：Output: mount: wrong fs type, bad option, bad superblock on ……
systemctl start rpcbind
systemctl enable rpcbind
mkdir /nfs/prometheus/data -p
mount -t nfs 192.168.16.100:/data/k8s /data/k8s

三、创建namespace 

vim ~/ns-monitor-namespace.yml (复制下面内容即可)

apiVersion: v1
kind: Namespace
metadata: 
  name: ns-monitor
  labels:
    name: ns-monitor

kubectl create -f ns-monitor-namespace.yml

四、安装node-exporter(用于采集kubernetes集群中各个节点的物理指标)

vim ~/node-exporter.yaml(复制下面内容即可)

kind: DaemonSet
apiVersion: apps/v1
metadata: 
  labels:
    app: node-exporter
  name: node-exporter
  namespace: ns-monitor
spec:
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: node-exporter
  template:
    metadata:
      labels:
        app: node-exporter
    spec:
      containers:
        - name: node-exporter
          image: prom/node-exporter:v0.16.0
          ports:
            - containerPort: 9100
              protocol: TCP
              name:	http
      hostNetwork: true
      hostPID: true
      tolerations:
        - effect: NoSchedule
          operator: Exists

---
kind: Service
apiVersion: v1
metadata:
  labels:
    app: node-exporter
  name: node-exporter-service
  namespace: ns-monitor
spec:
  ports:
    - name:	http
      port: 9100
      nodePort: 31672
      protocol: TCP
  type: NodePort
  selector:
    app: node-exporter

kubectl create -f node-exporter.yaml

五、安装prometheus

vim ~/prometheus.yaml (复制下面内容即可)

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: prometheus
rules:
  - apiGroups: [""] # "" indicates the core API group
    resources:
      - nodes
      - nodes/proxy
      - services
      - endpoints
      - pods
    verbs:
      - get
      - watch
      - list
  - apiGroups:
      - extensions
    resources:
      - ingresses
    verbs:
      - get
      - watch
      - list
  - nonResourceURLs: ["/metrics"]
    verbs:
      - get
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: prometheus
  namespace: ns-monitor
  labels:
    app: prometheus
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: prometheus
subjects:
  - kind: ServiceAccount
    name: prometheus
    namespace: ns-monitor
roleRef:
  kind: ClusterRole
  name: prometheus
  apiGroup: rbac.authorization.k8s.io
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: prometheus-conf
  namespace: ns-monitor
  labels:
    app: prometheus
data:
  prometheus.yml: |-
    # my global config
    global:
      scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
      evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
      # scrape_timeout is set to the global default (10s).

    # Alertmanager configuration
    alerting:
      alertmanagers:
      - static_configs:
        - targets:
          # - alertmanager:9093

    # Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
    rule_files:
      # - "first_rules.yml"
      # - "second_rules.yml"

    # A scrape configuration containing exactly one endpoint to scrape:
    # Here it's Prometheus itself.
    scrape_configs:
      # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
      - job_name: 'prometheus'

        # metrics_path defaults to '/metrics'
        # scheme defaults to 'http'.

        static_configs:
          - targets: ['localhost:9090']
      - job_name: 'grafana'
        static_configs:
          - targets:
              - 'grafana-service.ns-monitor:3000'

      - job_name: 'kubernetes-apiservers'

        kubernetes_sd_configs:
        - role: endpoints

        # Default to scraping over https. If required, just disable this or change to
        # `http`.
        scheme: https

        # This TLS & bearer token file config is used to connect to the actual scrape
        # endpoints for cluster components. This is separate to discovery auth
        # configuration because discovery & scraping are two separate concerns in
        # Prometheus. The discovery auth config is automatic if Prometheus runs inside
        # the cluster. Otherwise, more config options have to be provided within the
        # <kubernetes_sd_config>.
        tls_config:
          ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
          # If your node certificates are self-signed or use a different CA to the
          # master CA, then disable certificate verification below. Note that
          # certificate verification is an integral part of a secure infrastructure
          # so this should only be disabled in a controlled environment. You can
          # disable certificate verification by uncommenting the line below.
          #
          # insecure_skip_verify: true
        bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token

        # Keep only the default/kubernetes service endpoints for the https port. This
        # will add targets for each API server which Kubernetes adds an endpoint to
        # the default/kubernetes service.
        relabel_configs:
        - source_labels: [__meta_kubernetes_namespace, __meta_kubernetes_service_name, __meta_kubernetes_endpoint_port_name]
          action: keep
          regex: default;kubernetes;https

      # Scrape config for nodes (kubelet).
      #
      # Rather than connecting directly to the node, the scrape is proxied though the
      # Kubernetes apiserver.  This means it will work if Prometheus is running out of
      # cluster, or can't connect to nodes for some other reason (e.g. because of
      # firewalling).
      - job_name: 'kubernetes-nodes'

        # Default to scraping over https. If required, just disable this or change to
        # `http`.
        scheme: https

        # This TLS & bearer token file config is used to connect to the actual scrape
        # endpoints for cluster components. This is separate to discovery auth
        # configuration because discovery & scraping are two separate concerns in
        # Prometheus. The discovery auth config is automatic if Prometheus runs inside
        # the cluster. Otherwise, more config options have to be provided within the
        # <kubernetes_sd_config>.
        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:443
        - source_labels: [__meta_kubernetes_node_name]
          regex: (.+)
          target_label: __metrics_path__
          replacement: /api/v1/nodes/${1}/proxy/metrics

      # Scrape config for Kubelet cAdvisor.
      #
      # This is required for Kubernetes 1.7.3 and later, where cAdvisor metrics
      # (those whose names begin with 'container_') have been removed from the
      # Kubelet metrics endpoint.  This job scrapes the cAdvisor endpoint to
      # retrieve those metrics.
      #
      # In Kubernetes 1.7.0-1.7.2, these metrics are only exposed on the cAdvisor
      # HTTP endpoint; use "replacement: /api/v1/nodes/${1}:4194/proxy/metrics"
      # in that case (and ensure cAdvisor's HTTP server hasn't been disabled with
      # the --cadvisor-port=0 Kubelet flag).
      #
      # This job is not necessary and should be removed in Kubernetes 1.6 and
      # earlier versions, or it will cause the metrics to be scraped twice.
      - job_name: 'kubernetes-cadvisor'

        # Default to scraping over https. If required, just disable this or change to
        # `http`.
        scheme: https

        # This TLS & bearer token file config is used to connect to the actual scrape
        # endpoints for cluster components. This is separate to discovery auth
        # configuration because discovery & scraping are two separate concerns in
        # Prometheus. The discovery auth config is automatic if Prometheus runs inside
        # the cluster. Otherwise, more config options have to be provided within the
        # <kubernetes_sd_config>.
        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:443
        - source_labels: [__meta_kubernetes_node_name]
          regex: (.+)
          target_label: __metrics_path__
          replacement: /api/v1/nodes/${1}/proxy/metrics/cadvisor

      # Scrape config for service endpoints.
      #
      # The relabeling allows the actual service scrape endpoint to be configured
      # via the following annotations:
      #
      # * `prometheus.io/scrape`: Only scrape services that have a value of `true`
      # * `prometheus.io/scheme`: If the metrics endpoint is secured then you will need
      # to set this to `https` & most likely set the `tls_config` of the scrape config.
      # * `prometheus.io/path`: If the metrics path is not `/metrics` override this.
      # * `prometheus.io/port`: If the metrics are exposed on a different port to the
      # service then set this appropriately.
      - job_name: 'kubernetes-service-endpoints'

        kubernetes_sd_configs:
        - role: endpoints

        relabel_configs:
        - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scrape]
          action: keep
          regex: true
        - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scheme]
          action: replace
          target_label: __scheme__
          regex: (https?)
        - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_path]
          action: replace
          target_label: __metrics_path__
          regex: (.+)
        - source_labels: [__address__, __meta_kubernetes_service_annotation_prometheus_io_port]
          action: replace
          target_label: __address__
          regex: ([^:]+)(?::\d+)?;(\d+)
          replacement: $1:$2
        - action: labelmap
          regex: __meta_kubernetes_service_label_(.+)
        - source_labels: [__meta_kubernetes_namespace]
          action: replace
          target_label: kubernetes_namespace
        - source_labels: [__meta_kubernetes_service_name]
          action: replace
          target_label: kubernetes_name

      # Example scrape config for probing services via the Blackbox Exporter.
      #
      # The relabeling allows the actual service scrape endpoint to be configured
      # via the following annotations:
      #
      # * `prometheus.io/probe`: Only probe services that have a value of `true`
      - job_name: 'kubernetes-services'

        metrics_path: /probe
        params:
          module: [http_2xx]

        kubernetes_sd_configs:
        - role: service

        relabel_configs:
        - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_probe]
          action: keep
          regex: true
        - source_labels: [__address__]
          target_label: __param_target
        - target_label: __address__
          replacement: blackbox-exporter.example.com:9115
        - source_labels: [__param_target]
          target_label: instance
        - action: labelmap
          regex: __meta_kubernetes_service_label_(.+)
        - source_labels: [__meta_kubernetes_namespace]
          target_label: kubernetes_namespace
        - source_labels: [__meta_kubernetes_service_name]
          target_label: kubernetes_name

      # Example scrape config for probing ingresses via the Blackbox Exporter.
      #
      # The relabeling allows the actual ingress scrape endpoint to be configured
      # via the following annotations:
      #
      # * `prometheus.io/probe`: Only probe services that have a value of `true`
      - job_name: 'kubernetes-ingresses'

        metrics_path: /probe
        params:
          module: [http_2xx]

        kubernetes_sd_configs:
          - role: ingress

        relabel_configs:
          - source_labels: [__meta_kubernetes_ingress_annotation_prometheus_io_probe]
            action: keep
            regex: true
          - source_labels: [__meta_kubernetes_ingress_scheme,__address__,__meta_kubernetes_ingress_path]
            regex: (.+);(.+);(.+)
            replacement: ${1}://${2}${3}
            target_label: __param_target
          - target_label: __address__
            replacement: blackbox-exporter.example.com:9115
          - source_labels: [__param_target]
            target_label: instance
          - action: labelmap
            regex: __meta_kubernetes_ingress_label_(.+)
          - source_labels: [__meta_kubernetes_namespace]
            target_label: kubernetes_namespace
          - source_labels: [__meta_kubernetes_ingress_name]
            target_label: kubernetes_name

      # Example scrape config for pods
      #
      # The relabeling allows the actual pod scrape endpoint to be configured via the
      # following annotations:
      #
      # * `prometheus.io/scrape`: Only scrape pods that have a value of `true`
      # * `prometheus.io/path`: If the metrics path is not `/metrics` override this.
      # * `prometheus.io/port`: Scrape the pod on the indicated port instead of the
      # pod's declared ports (default is a port-free target if none are declared).
      - job_name: 'kubernetes-pods'

        kubernetes_sd_configs:
        - role: pod

        relabel_configs:
        - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]
          action: keep
          regex: true
        - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]
          action: replace
          target_label: __metrics_path__
          regex: (.+)
        - source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]
          action: replace
          regex: ([^:]+)(?::\d+)?;(\d+)
          replacement: $1:$2
          target_label: __address__
        - action: labelmap
          regex: __meta_kubernetes_pod_label_(.+)
        - source_labels: [__meta_kubernetes_namespace]
          action: replace
          target_label: kubernetes_namespace
        - source_labels: [__meta_kubernetes_pod_name]
          action: replace
          target_label: kubernetes_pod_name
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: prometheus-rules
  namespace: ns-monitor
  labels:
    app: prometheus
data:
  cpu-usage.rule: |
    groups:
      - name: NodeCPUUsage
        rules:
          - alert: NodeCPUUsage
            expr: (100 - (avg by (instance) (irate(node_cpu{name="node-exporter",mode="idle"}[5m])) * 100)) > 75
            for: 2m
            labels:
              severity: "page"
            annotations:
              summary: "{{$labels.instance}}: High CPU usage detected"
              description: "{{$labels.instance}}: CPU usage is above 75% (current value is: {{ $value }})"
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: "prometheus-data-pv"
  labels:
    name: prometheus-data-pv
    release: stable
spec:
  capacity:
    storage: 5Gi
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Recycle
  nfs:
    path: /nfs/prometheus/data
    server: 192.168.228.128

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: prometheus-data-pvc
  namespace: ns-monitor
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi
  selector:
    matchLabels:
      name: prometheus-data-pv
      release: stable

---
kind: Deployment
apiVersion: apps/v1
metadata:
  labels:
    app: prometheus
  name: prometheus
  namespace: ns-monitor
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: prometheus
  template:
    metadata:
      labels:
        app: prometheus
    spec:
      serviceAccountName: prometheus
      securityContext:
        runAsUser: 0
      containers:
        - name: prometheus
          image: prom/prometheus:latest
          imagePullPolicy: IfNotPresent
          volumeMounts:
            - mountPath: /prometheus
              name: prometheus-data-volume
            - mountPath: /etc/prometheus/prometheus.yml
              name: prometheus-conf-volume
              subPath: prometheus.yml
            - mountPath: /etc/prometheus/rules
              name: prometheus-rules-volume
          ports:
            - containerPort: 9090
              protocol: TCP
      volumes:
        - name: prometheus-data-volume
          persistentVolumeClaim:
            claimName: prometheus-data-pvc
        - name: prometheus-conf-volume
          configMap:
            name: prometheus-conf
        - name: prometheus-rules-volume
          configMap:
            name: prometheus-rules
      tolerations:
        - key: node-role.kubernetes.io/master
          effect: NoSchedule

---
kind: Service
apiVersion: v1
metadata:
  annotations:
    prometheus.io/scrape: 'true'
  labels:
    app: prometheus
  name: prometheus-service
  namespace: ns-monitor
spec:
  ports:
    - port: 9090
      targetPort: 9090
  selector:
    app: prometheus
  type: NodePort

prometheus.yaml修改nfs的地址为nfs服务器的地址 （大约第386行）
nfs:
    path: /nfs/prometheus/data
    server: 192.168.0.102
kubectl create -f prometheus.yaml
检查是否成功运行 kubectl get pod -n ns-monitor

如果一直显示ContainerCreating，则可以执行kubectl describe pod prometheus-5c649bfcf4-crch2 -n ns-monitor  检查一下是否是nfs未连接上的问题

六、安装grafana

vim ~/grafana.yaml (复制下面内容即可)

apiVersion: v1
kind: PersistentVolume
metadata:
  name: "grafana-data-pv"
  labels:
    name: grafana-data-pv
    release: stable
spec:
  capacity:
    storage: 5Gi
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Recycle
  nfs:
    path: /nfs/grafana/data
    server: 192.168.228.128
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: grafana-data-pvc
  namespace: ns-monitor
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi
  selector:
    matchLabels:
      name: grafana-data-pv
      release: stable
---
kind: Deployment
apiVersion: apps/v1
metadata:
  labels:
    app: grafana
  name: grafana
  namespace: ns-monitor
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: grafana
  template:
    metadata:
      labels:
        app: grafana
    spec:
      securityContext:
        runAsUser: 0
      containers:
        - name: grafana
          image: grafana/grafana:latest
          imagePullPolicy: IfNotPresent
          env:
            - name: GF_AUTH_BASIC_ENABLED
              value: "true"
            - name: GF_AUTH_ANONYMOUS_ENABLED
              value: "false"
          readinessProbe:
            httpGet:
              path: /login
              port: 3000
          volumeMounts:
            - mountPath: /var/lib/grafana
              name: grafana-data-volume
          ports:
            - containerPort: 3000
              protocol: TCP
      volumes:
        - name: grafana-data-volume
          persistentVolumeClaim:
            claimName: grafana-data-pvc
---
kind: Service
apiVersion: v1
metadata:
  labels:
    app: grafana
  name: grafana-service
  namespace: ns-monitor
spec:
  ports:
    - port: 3000
      targetPort: 3000
      nodePort: 30001
  selector:
    app: grafana
  type: NodePort

grafana.yaml修改nfs的地址为nfs服务器的地址 （大约第16行）
nfs:
    path: /nfs/grafana/data
    server: 192.168.0.102
kubectl create -f grafana.yaml
检查是否成功运行 kubectl get pod -n ns-monitor

七、登陆

注意：打开30001防火墙端口或配置安全组

账号密码：admin/admin

八、配置

1、添加prometheus数据源

数据源选择prometheus，url地址填写：http://prometheus-service.ns-monitor:9090

 

 2、添加控制面板


输入地址：

集群监控：

docker monitor:https://grafana.com/grafana/dashboards/193

https://grafana.com/grafana/dashboards/315   点击load

Node Exporter Full:https://grafana.com/grafana/dashboards/1860

NGINX Ingress controller：https://grafana.com/grafana/dashboards/9614

Node Exporter for Prometheus Dashboard：https://grafana.com/grafana/dashboards/11074（推荐）

 选择prometheus数据源，导入。即可看到精美的监控页面

 

  更多精美监控页面请参考：Dashboards | Grafana Labs

 九、常见问题：

1、如果kubectl get pod发现pod一直Pending


则执行kubectl describe pods grafana-5567c66c9d-rcbdz  -n ns-monitor查询pod详细信息


如果提示0/1 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.
表明pod无法在master节点上分配，master节点具有pod无法容忍的污点
使用kubectl describe nodes查看节点明细，如下内容表示（不接受调度pod）
Name: linux
Taints: node-role.kubernetes.io/master:NoSchedule


删除这个污点命令：kubectl taint nodes tencent-centos7 node-role.kubernetes.io/master:NoSchedule-

相反设置master为调度污点的命令：

kubectl taint nodes master1 node-role.kubernetes.io/master=:NoSchedule

取值：

NoSchedule: 一定不能被调度

PreferNoSchedule: 尽量不要调度

NoExecute: 不仅不会调度, 还会驱逐Node上已有的Pod

注意：如果有污点始终无法删除，说明kubelet服务本身有问题

使用systemctl status kubelet查看一下

估计应该是hostname问题，参考（hostname变为bogon）

 


                

        

        

    

  


    

      

        

            

              
                
                  现实、太残忍
                
              
            

            

                关注
              
            

        

        

          
      

      

            

                专栏目录
          









                



	

		

			

				
					
k8s v1.26.0 搭建prometheus+grafana监控集群

				
			

			

				

					weixin_40548182的博客
				

				

					04-03
					
					505
					
				

			

		

		

			
				
文章末尾有prometheus监控k8s用到的yaml资源清单，包括报警配置等。

			
		

	



                

              
                



	

		

			

				
					
搭建 Prometheus+Grafana 的云平台监控系统

				
			

			

				

					weixin_44194491的博客
				

				

					11-14
					
					3508
					
				

			

		

		

			
				
1.1.1 Prometheus 概述
Prometheus（普罗米修斯）是一套开源的监控&报警&时间序列数据库的组合，起始是由
SoundCloud 公司开发的。现在最常见的 Docker、Mesos、Kubernetes 容器管理系统中，通常会搭配
Prometheus 进行监控。
Prometheus 基本原理是通过 HTTP 协议周期性抓取被监控组件的状态，这样做的好处是任...

			
		

	



                


  
              

                


	

		

			

				
					
【IT运维】普罗米修斯基本介绍及监控平台部署（Prometheus+Grafana）_普罗米修斯监控

				
			

			

				

					2301_77118221的博客
				

				

					05-02
					
					1534
					
				

			

		

		

			
				
Pull方式的优势是能够自动进行上游监控和水平监控，配置更少，更容易扩展，更灵活，更容易实现高可用。简单来说就是Pull方式可以降低耦合。由于在推送系统中很容易出现因为向监控系统推送数据失败而导致被监控系统瘫痪的问题。因为如果同一时间有很多被监控主机都把数据推送给监控主机的话，就很可能导致监控主机处理不过来，所以通过Pull方式，被采集端无需感知监控系统的存在，完全独立于监控系统之外，这样数据的采集完全由监控系统控制。

			
		

	





	

		

			

				
					
kubernetes部署grafana

				
			

			

				

					认知 行动 坚持
				

				

					06-22
					
					1519
					
				

			

		

		

			
				
Grafana是一款流行的开源可视化平台，它支持与多种监控系统的集成，如Prometheus、Zabbix等。使用kubernetes来部署grafana服务。亲测可用。

			
		

	



		

			
		



	

		

			

				
					
(16)prometheus（普罗米修斯）监控的搭建

				
			

			

				

					2201_75745826的博客
				

				

					08-19
					
					1752
					
				

			

		

		

			
				
granfana是一种可视化工具，将数据图形化，可以结合prometheus、zabbix的数据脚本和参数，形成图形化和告警。官网：

			
		

	





	

		

			

				
					
Linux部署Prometheus+Grafana

				
			

			

				

					Hard work results, technology is willing to dream
				

				

					07-18
					
					2470
					
				

			

		

		

			
				
Prometheus+Grafana

			
		

	





	

		

			

				
					
Kubernetes 1.7  部署 Prometheus 监控服务

				
			

			

				

					shida's blog
				

				

					05-07
					
					1337
					
				

			

		

		

			
				
一、背景简介       原生的 Kubernetes 是集成的 InfluxDB + Heapster + Grafana 监控组件，存在一定局限；       本文主要介绍，在 Kubernetes 集群中部署 Prometheus 监控系统的一般方法（核心功能安装）二、基本步骤2.1  镜像准备      prom/prometheus:v1.7.0  【主监控程序】      prom/a...

			
		

	





	

		

			

				
					
使用 Docker 部署 Prometheus + Grafana 监控平台

				
			

			

				

					2401_84046912的博客
				

				

					04-05
					
					980
					
				

			

		

		

			
				
这份文档从构建一个键值数据库的关键架构入手，不仅带你建立起全局观，还帮你迅速抓住核心主线。除此之外，还会具体讲解数据结构、线程模型、网络框架、持久化、主从同步和切片集群等，帮你搞懂底层原理。相信这对于所有层次的Redis使用者都是一份非常完美的教程了。你的支持，我的动力；祝各位前程似锦，offer不断！！！《一线大厂Java面试题解析+核心总结学习笔记+最新讲解视频+实战项目源码》点击传送门即可获取！之外，还会具体讲解数据结构、线程模型、网络框架、持久化、主从同步和切片集群等，帮你搞懂底层原理。

			
		

	





	

		

			

				
					
grafana java插件_使用Prometheus + Grafana搭建监控系统

				
			

			

				

					weixin_35968185的博客
				

				

					02-26
					
					335
					
				

			

		

		

			
				
对任何系统就像人一样需要“知己知彼“才能做到”百战百胜”，经常在讨论高可用，一方面需要从架构设计、编码实施、质量验证等环节保证项目的高可用，另一方面能够尽可能早的发现问题也是非常的重要。目前监控生态中有大量的产品可供选择，Java生态尤其是Spring Boot生态下更是，如何选择一套适合自己的方案则显得尤为重要。对于Spring Boot应用可以使用Spring Boot Admin进行监控，但...

			
		

	





	

		

			

				
					
k8s使用rancher做面板，安装prometheus+grafana监控

				
			

			

				

					weixin_42660934的博客
				

				

					08-06
					
					3143
					
				

			

		

		

			
				
前提：
1，k8s自带的dashboard界面不友好，使用不方便，安装rancher页面，方便使用，同时rancher支持多种监控一件安装，cicd一键集成，极大方便了使用者。
2，rancher使用rancher自定义证书，方便安装，使用域名testing-k8s.yunwei.com，端口30443,服务器ip172.21.1.48
3，使用helm安装。helm是类似yum的安装工具，推荐用helm安装，再进行修改定制。
安装步骤：
1，创建专用命名空间
kubectl create ns cattl

			
		

	





	

		

			

				
					
监控部署---普罗米修斯+grafana (超详细)

				
			

			

				

					Zisson_no_error的博客
				

				

					06-07
					
					7469
					
				

			

		

		

			
				
以验证成功，部署一步到位，自己一步一步编写的文章！觉得有效的请点个赞

			
		

	





	

		

			

				
					
Prometheus 监控平台（Prometheus Monitoring Platform）

					
最新发布

				
			

			

				

					Linux运维老纪的博客
				

				

					09-13
					
					1047
					
				

			

		

		

			
				
Prometheus（普罗米修斯）是一个最初在 SoundCloud 上构建的监控系统。自 2012
年成为社区开源项目，拥有非常活跃的开发人员和用户社区。为强调开源及独立维护，
Prometheus 于 2016 年加入云原生云计算基金会（CNCF），成为继 Kubernetes 之后的第
二个托管项目。本章详细介绍prometheus监控部署。

			
		

	





	

		

			

				
					
Promethues （普罗米修斯）详细介绍

					
热门推荐

				
			

			

				

					weixin_71429844的博客
				

				

					10-25
					
					4万+
					
				

			

		

		

			
				
Promethues （普罗米修斯）详细介绍

			
		

	





	

		

			

				
					
k8s1.19.7部署prometheus+grafana

				
			

			

				

					hatestrawberry的博客
				

				

					01-30
					
					463
					
				

			

		

		

			
				
cat > node-exporter.yaml  <<EOF
---
apiVersion: v1
kind: ReplicationController
metadata:
  name: node-exporter
  namespace: kube-system
  labels:
    k8s-app: node-exporter
spec:
  replicas: 1
  selector:
    k8s-app: node-exporter
  template:
   

			
		

	





	

		

			

				
					
Prometheus普罗米修斯-数据可视化监控平台搭建

				
			

			

				

					qq_21794989的博客
				

				

					03-05
					
					2672
					
				

			

		

		

			
				
实际工作中遇到问题，有感而发总比单纯学习更要有更大的认知影响、更深的知识印象和更具体的实际意义，因此工作之余多学习也不仅指多纯（无目的）扩展知识面，而更应该是自己所处行业相关业务、技术等的纵向扩展和以实际意义的问题出发讨论、思考、总结。建议下载安装包免安装模式（由于默认安装模式会注册服务grafana-server和grafana，开机自启动，还需要进入services.msc进行修改），自行进入bin路劲cmd通过grafana-server启动，如果像一劳永逸直接安装模式+开机自启动。

			
		

	





	

		

			

				
					
完美的分布式监控系统——Prometheus（普罗米修斯）与优雅的开源可视化平台——Grafana（格鲁夫娜）

				
			

			

				

					阿丹的博客
				

				

					08-08
					
					2095
					
				

			

		

		

			
				
prometheus与grafana之间是相辅相成的关系。作为完美的分布式监控系统的Prometheus，就想布加迪威龙一样示例和动力强劲。在猛的车也少不了仪表盘来观察。于是优雅的可视化平台Grafana出现了。简而言之Grafana作为可视化的平台，平台的数据从Prometheus中取到来进行仪表盘的展示。而Prometheus这源源不断的给Grafana提供数据的支持。

			
		

	





	

		

			

				
					
kube-Prometheus安装和使用完全教程

				
			

			

				

					qq_40406649的博客
				

				

					01-23
					
					3195
					
				

			

		

		

			
				
kube-Prometheus是一个全面集成的Kubernetes集群监控解决方案，它将核心的Prometheus组件、Grafana可视化面板以及Prometheus规则等资源精心编排并集成为一个易于部署和管理的整体。该项目通过GitHub仓库提供了详尽的Kubernetes清单文件、Grafana仪表板配置和Prometheus规则，辅以详细的文档和脚本，使得在Kubernetes集群中利用Prometheus进行端到端的监控变得异常便捷高效。更进一步，kube-Prometheus不仅引入了Prome

			
		

	





	

		

			

				
					
普罗米修斯(prometheus)应用

				
			

			

				

					ChenHuaiJie0912的博客
				

				

					03-20
					
					2098
					
				

			

		

		

			
				
普罗米修斯是一套开源的监控系统，可以监控啥呢？如下：

linux服务器

开源软件，如redis、mysql

你自己写的项目

一、安装go语言环境

官网地址:https://golang.org

下载：wget https://dl.google.com/go/go1.11.2.linux-amd64.tar.gz

下载完毕后，解压 tar -zxvf go1.11.2.linux-amd64.tar.gz

配置环境变量：

vim /etc/profile

在最后添加

export GO

			
		

	





	

		

			

				
					
docker-compose编写promethus+Grafana监控

				
			

			

				

					03-25
				

			

		

		

			
				
答：以下是一个示例的docker-compose.yml文件，用于启动Prometheus和Grafana来监控一个或多个应用程序：  ``` version: '3' services:  prometheus:  image: prom/prometheus  container_name: prometheus  ports:  ...

			
		

	



              




          




        



    





    



      

      

        
      

      





	

		评论	
	

	
	




  

    

      添加红包
      
    

    

      

        
        

          
          
        

        
请填写红包祝福语或标题

      

      

        
        

          
          个
        

        
红包个数最小为10个

      

      

        
        

          
          元
        

        
红包金额最低5元

      

      

        
        

          当前余额3.43元
          前往充值 >
        

      

      

        

          需支付：10.00元
        

        
        
      

    

  





  

    
    
  

  

    
    
  








  

    

      

        

          

            
            
成就一亿技术人!

          

          

        

        

          

          

            领取后你会自动成为博主和红包主的粉丝
            规则
          

        

      

      

        

          

            
              
            
            

              
hope_wisdom
 发出的红包
            

          

        

        

          

          

          

        

      

    

    

  



      
      

      
实付元

      
使用余额支付

      

        

          

            
            点击重新获取
          

        

        
扫码支付

      

      

        
          
            
          
          
        
      

      

        
        钱包余额
          0
          

            
            

              

                
抵扣说明：

                
 1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
 2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

              

            

          

      

      余额充值