Prometheus+Grafana+Alertmanager搭建全方位的監控告警系統

尹瑞星發表於2021-02-26

PrometheusGrafana

prometheus安裝和配置

prometheus元件介紹

1.Prometheus Server: 用於收集和儲存時間序列資料。

2.Client Library: 客戶端庫，檢測應用程式程式碼，當Prometheus抓取例項的HTTP端點時，客戶端庫會將所有跟蹤的metrics指標的當前狀態傳送到prometheus server端。

3.Exporters: prometheus支援多種exporter，通過exporter可以採集metrics資料，然後傳送到prometheus server端

4.Alertmanager: 從 Prometheus server 端接收到 alerts 後，會進行去重，分組，並路由到相應的接收方，發出報警，常見的接收方式有：電子郵件，微信，釘釘, slack等。

5.Grafana：監控儀表盤

6.pushgateway: 各個目標主機可上報資料到pushgatewy，然後prometheus server統一從pushgateway拉取資料。

prometheus架構圖

　　從上圖可發現，Prometheus整個生態圈組成主要包括prometheus server，Exporter，pushgateway，alertmanager，grafana，Web ui介面，Prometheus server由三個部分組成，Retrieval，Storage，PromQL 。

retrieval負責在活躍的target主機上抓取監控指標資料
storage主要是把採集到的資料儲存到磁碟中
promQL是prometheus提供的查詢語言模組

prometheus工作流程

Prometheus server可定期從活躍的（up）目標主機上（target）拉取監控指標資料，目標主機的監控資料可通過配置靜態job或者服務發現的方式被prometheus server採集到，這種方式預設的pull方式拉取指標；也可通過pushgateway把採集的資料上報到prometheus server中；還可通過一些元件自帶的exporter採集相應元件的資料；
Prometheus server把採集到的監控指標資料儲存到本地磁碟或者資料庫；
Prometheus採集的監控指標資料按時間序列儲存，通過配置報警規則，把觸發的報警傳送到alertmanager
Alertmanager通過配置報警接收方，傳送報警到郵件，微信或者釘釘等
Prometheus 自帶的web ui介面提供PromQL查詢語言，可查詢監控資料
Grafana可接入prometheus資料來源，把監控資料以圖形化形式展示出

安裝node-exporter元件

node-exporter是採集機器（物理機、虛擬機器、雲主機等）的監控指標資料，能夠採集到的指標包括CPU, 記憶體，磁碟，網路，檔案數等資訊。

實驗環境

一個master節點，一個node節點。

在master節點操作

cat >node-export.yaml  <<EOF
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: node-exporter
  namespace: monitor-sa
  labels:
    name: node-exporter
spec:
  selector:
    matchLabels:
     name: node-exporter
  template:
    metadata:
      labels:
        name: node-exporter
    spec:
      hostPID: true
      hostIPC: true
      hostNetwork: true
      containers:
      - name: node-exporter
        image: prom/node-exporter:v0.16.0
        ports:
        - containerPort: 9100
        resources:
          requests:
            cpu: 0.15
        securityContext:
          privileged: true
        args:
        - --path.procfs
        - /host/proc
        - --path.sysfs
        - /host/sys
        - --collector.filesystem.ignored-mount-points
        - '"^/(sys|proc|dev|host|etc)($|/)"'
        volumeMounts:
        - name: dev
          mountPath: /host/dev
        - name: proc
          mountPath: /host/proc
        - name: sys
          mountPath: /host/sys
        - name: rootfs
          mountPath: /rootfs
      tolerations:
      - key: "node-role.kubernetes.io/master"
        operator: "Exists"
        effect: "NoSchedule"
      volumes:
        - name: proc
          hostPath:
            path: /proc
        - name: dev
          hostPath:
            path: /dev
        - name: sys
          hostPath:
            path: /sys
        - name: rootfs
          hostPath:
            path: /
EOF

通過node-exporter採集資料

curl http://主機ip:9100/metrics

在k8s叢集中部署promethues

建立namespace、sa賬號，在k8s叢集的master節點操作

kubectl create ns monitor-sa
kubectl create serviceaccount monitor -n monitor-sa
#把sa賬號monitor通過clusterrolebing繫結到clusterrole上
kubectl create clusterrolebinding moniror-clusterrolebinding -n monitor-sa --clusterrole=cluster-admin --serviceaccount=monitor-sa:monitor

建立資料目錄

# 在k8s叢集的任何一個node節點操作，本實驗在node1上操作
mkdir /data
chmod 777 /data/

安裝prometheus，在master節點操作

#建立一個configmap儲存卷，用來存放prometheus配置資訊
#prometheus-cfg.yaml
kind: ConfigMap
apiVersion: v1
metadata:
  labels:
    app: prometheus
  name: prometheus-config
  namespace: monitor-sa
data:
  prometheus.yml: |
    global:
      scrape_interval: 15s
      scrape_timeout: 10s
      evaluation_interval: 1m
    scrape_configs:
    - job_name: 'kubernetes-node'
      kubernetes_sd_configs:
      - role: node
      relabel_configs:
      - source_labels: [__address__]
        regex: '(.*):10250'
        replacement: ':9100'
        target_label: __address__
        action: replace
      - action: labelmap
        regex: __meta_kubernetes_node_label_(.+)
    - job_name: 'kubernetes-node-cadvisor'
      kubernetes_sd_configs:
      - role:  node
      scheme: https
      tls_config:
        ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
      bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
      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//proxy/metrics/cadvisor
    - job_name: 'kubernetes-apiserver'
      kubernetes_sd_configs:
      - role: endpoints
      scheme: https
      tls_config:
        ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
      bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
      relabel_configs:
      - source_labels: [__meta_kubernetes_namespace, __meta_kubernetes_service_name, __meta_kubernetes_endpoint_port_name]
        action: keep
        regex: default;kubernetes;https
    - 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: :
      - 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 
---
#通過deployment部署prometheus
#prometheus-deploy.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: prometheus-server
  namespace: monitor-sa
  labels:
    app: prometheus
spec:
  replicas: 1
  selector:
    matchLabels:
      app: prometheus
      component: server
  template:
    metadata:
      labels:
        app: prometheus
        component: server
      annotations:
        prometheus.io/scrape: 'false'
    spec:
      nodeName: node1
      serviceAccountName: monitor
      containers:
      - name: prometheus
        image: prom/prometheus:v2.2.1
        imagePullPolicy: IfNotPresent
        command:
          - prometheus
          - --config.file=/etc/prometheus/prometheus.yml
          - --storage.tsdb.path=/prometheus
          - --storage.tsdb.retention=720h
        ports:
        - containerPort: 9090
          protocol: TCP
        volumeMounts:
        - mountPath: /etc/prometheus/prometheus.yml
          name: prometheus-config
          subPath: prometheus.yml
        - mountPath: /prometheus/
          name: prometheus-storage-volume
      volumes:
        - name: prometheus-config
          configMap:
            name: prometheus-config
            items:
              - key: prometheus.yml
                path: prometheus.yml
                mode: 0644
        - name: prometheus-storage-volume
          hostPath:
           path: /data
           type: Directory

注意：通過上面命令生成的promtheus-cfg.yaml檔案會有一些問題，$1和$2這種變數在檔案裡沒有，需要在k8s的master1節點開啟promtheus-cfg.yaml檔案，手動把$1和$2這種變數寫進檔案裡，promtheus-cfg.yaml檔案需要手動修改部分如下：

22行的replacement: ':9100'變成replacement: '${1}:9100'
42行的replacement: /api/v1/nodes//proxy/metrics/cadvisor變成
              replacement: /api/v1/nodes/${1}/proxy/metrics/cadvisor
73行的replacement:  變成replacement: $1:$2

給prometheus pod 建立一個service

cat  > prometheus-svc.yaml << EOF
---
apiVersion: v1
kind: Service
metadata:
  name: prometheus
  namespace: monitor-sa
  labels:
    app: prometheus
spec:
  type: NodePort
  ports:
    - port: 9090
      targetPort: 9090
      protocol: TCP
  selector:
    app: prometheus
    component: server
EOF

#檢視service在物理機對映的埠
kubectl	get svc -n monitor-sa

#訪問prometheus web ui 介面
http://172.16.9.3:30426/graph
#點選頁面的Status->Targets，可看到如下,說明我們配置的服務發現可以正常採集資料

prometheus熱更新

#為了每次修改配置檔案可以熱載入prometheus，也就是不停止prometheus，就可以使配置生效，如修改prometheus-cfg.yaml，想要使配置生效可用如下熱載入命令：
curl -X POST http://10.244.1.125:9090/-/reload

#10.244.1.66是prometheus的pod的ip地址

#熱載入速度比較慢，可以暴力重啟prometheus，如修改上面的prometheus-cfg.yaml檔案之後，可執行如下強制刪除：

kubectl delete -f prometheus-cfg.yaml

kubectl delete -f prometheus-deploy.yaml

然後再通過apply更新：

kubectl apply -f prometheus-cfg.yaml

kubectl apply -f prometheus-deploy.yaml

注意：

線上最好熱載入，暴力刪除可能造成監控資料的丟失

Grafana安裝和配置

下載安裝Grafana需要的映象

上傳heapster-grafana-amd64_v5_0_4.tar.gz映象到k8s的各個master節點和k8s的各個node節點，然後在各個節點手動解壓：
docker load -i heapster-grafana-amd64_v5_0_4.tar.gz

映象所在的百度網盤地址如下：

連結：https://pan.baidu.com/s/1TmVGKxde_cEYrbjiETboEA 提取碼：052u

在k8s的master節點建立grafana.yaml

cat  >grafana.yaml <<  EOF
apiVersion: apps/v1
kind: Deployment
metadata:
  name: monitoring-grafana
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      task: monitoring
      k8s-app: grafana
  template:
    metadata:
      labels:
        task: monitoring
        k8s-app: grafana
    spec:
      containers:
      - name: grafana
        image: k8s.gcr.io/heapster-grafana-amd64:v5.0.4
        ports:
        - containerPort: 3000
          protocol: TCP
        volumeMounts:
        - mountPath: /etc/ssl/certs
          name: ca-certificates
          readOnly: true
        - mountPath: /var
          name: grafana-storage
        env:
        - name: INFLUXDB_HOST
          value: monitoring-influxdb
        - name: GF_SERVER_HTTP_PORT
          value: "3000"
          # The following env variables are required to make Grafana accessible via
          # the kubernetes api-server proxy. On production clusters, we recommend
          # removing these env variables, setup auth for grafana, and expose the grafana
          # service using a LoadBalancer or a public IP.
        - name: GF_AUTH_BASIC_ENABLED
          value: "false"
        - name: GF_AUTH_ANONYMOUS_ENABLED
          value: "true"
        - name: GF_AUTH_ANONYMOUS_ORG_ROLE
          value: Admin
        - name: GF_SERVER_ROOT_URL
          # If you're only using the API Server proxy, set this value instead:
          # value: /api/v1/namespaces/kube-system/services/monitoring-grafana/proxy
          value: /
      volumes:
      - name: ca-certificates
        hostPath:
          path: /etc/ssl/certs
      - name: grafana-storage
        emptyDir: {}
---
apiVersion: v1
kind: Service
metadata:
  labels:
    # For use as a Cluster add-on (https://github.com/kubernetes/kubernetes/tree/master/cluster/addons)
    # If you are NOT using this as an addon, you should comment out this line.
    kubernetes.io/cluster-service: 'true'
    kubernetes.io/name: monitoring-grafana
  name: monitoring-grafana
  namespace: kube-system
spec:
  # In a production setup, we recommend accessing Grafana through an external Loadbalancer
  # or through a public IP.
  # type: LoadBalancer
  # You could also use NodePort to expose the service at a randomly-generated port
  # type: NodePort
  ports:
  - port: 80
    targetPort: 3000
  selector:
    k8s-app: grafana
  type: NodePort
EOF

通過kubectl get sac -n cube-system看到grafana暴漏的蘇主機埠是32351，我們可以訪問k8s叢集的master節點ip:32351即可訪問grafana的web介面

Grafana介面接入prometheus資料來源

登入Grafana,172.16.9.3:32351，賬號密碼都是admin
配置grafana介面，選擇create your first data source
```
Name:Prometheus
Type:Prometheus
HTTP出的URL：http://prometheus.monitor-sa.svc:9090
```
點選左下角Save&Test，出現Data source is working，說明prometheus資料來源成功的被grafana接入了。

匯入監控模板，可在如下連結搜尋
https://grafana.com/dashboards?dataSource=prometheus&search=kubernetes
也可直接匯入node_exporter.json監控模板，這個可以把node節點指標顯示出來，node_exporter.json在百度網盤地址如下：
```
連結：https://pan.baidu.com/s/1vF1kAMRbxQkUGPlZt91MWg 提取碼：kyd6
```
還可直接匯入docker_rev1.json，可以把容器相關的資料展示出來
docker_rev1.json在百度網盤地址如下
```
連結：https://pan.baidu.com/s/17o_nja5N2R-g9g5PkJ3aFA 提取碼：vinv
```
匯入監控模版步驟：點選左側+號下面的Import，選擇Upload json file,選擇一個本地的json檔案即可。

安裝配置kube-state-metrics元件

kube-state-metrics通過監聽API Server生成有關資源物件的狀態指標，比如Deployment、Node、Pod，需要注意的是kube-state-metrics只是簡單的提供一個metrics資料，並不會儲存這些指標資料，所以我們可以使用Prometheus來抓取這些資料然後儲存，主要關注的是業務相關的一些後設資料，比如Deployment、Pod、副本狀態等；排程了多少個replicas？現在可用的有幾個？多少個Pod是running/stopped/terminated狀態？Pod重啟了多少次？我有多少job在執行中。

安裝kube-state-metrics元件

建立sa，並對sa授權，在master節點操作

cat > kube-state-metrics-rbac.yaml <<EOF
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: kube-state-metrics
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: kube-state-metrics
rules:
- apiGroups: [""]
  resources: ["nodes", "pods", "services", "resourcequotas", "replicationcontrollers", "limitranges", "persistentvolumeclaims", "persistentvolumes", "namespaces", "endpoints"]
  verbs: ["list", "watch"]
- apiGroups: ["extensions"]
  resources: ["daemonsets", "deployments", "replicasets"]
  verbs: ["list", "watch"]
- apiGroups: ["apps"]
  resources: ["statefulsets"]
  verbs: ["list", "watch"]
- apiGroups: ["batch"]
  resources: ["cronjobs", "jobs"]
  verbs: ["list", "watch"]
- apiGroups: ["autoscaling"]
  resources: ["horizontalpodautoscalers"]
  verbs: ["list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: kube-state-metrics
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: kube-state-metrics
subjects:
- kind: ServiceAccount
  name: kube-state-metrics
  namespace: kube-system
EOF

安裝cube-state-metrics元件，在master節點操作

cat > kube-state-metrics-deploy.yaml <<EOF
apiVersion: apps/v1
kind: Deployment
metadata:
  name: kube-state-metrics
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      app: kube-state-metrics
  template:
    metadata:
      labels:
        app: kube-state-metrics
    spec:
      serviceAccountName: kube-state-metrics
      containers:
      - name: kube-state-metrics
#        image: gcr.io/google_containers/kube-state-metrics-amd64:v1.3.1
        image: quay.io/coreos/kube-state-metrics:v1.9.0
        ports:
        - containerPort: 8080
EOF

建立service，在master節點操作

cat >kube-state-metrics-svc.yaml <<EOF
apiVersion: v1
kind: Service
metadata:
  annotations:
    prometheus.io/scrape: 'true'
  name: kube-state-metrics
  namespace: kube-system
  labels:
    app: kube-state-metrics
spec:
  ports:
  - name: kube-state-metrics
    port: 8080
    protocol: TCP
  selector:
    app: kube-state-metrics
EOF

在Grafana web介面匯入kubernetes Cluster和kubernetes cluster monitoring

連結：https://pan.baidu.com/s/1QAMqT8scsXx-lzEPI6MPgA 
提取碼：i4yd

安裝和配置Alertmanager-傳送報警到qq郵箱

在k8s的master節點建立alertmanager-cm.yaml檔案

cat >alertmanager-cm.yaml <<EOF
kind: ConfigMap
apiVersion: v1
metadata:
  name: alertmanager
  namespace: monitor-sa
data:
  alertmanager.yml: |-
    global:
      resolve_timeout: 1m
      smtp_smarthost: 'smtp.163.com:25'
      smtp_from: '15011572657@163.com'
      smtp_auth_username: '15011572657'
      smtp_auth_password: 'BDBPRMLNZGKWRFJP'
      smtp_require_tls: false
    route:
      group_by: [alertname]
      group_wait: 10s
      group_interval: 10s
      repeat_interval: 10m
      receiver: default-receiver
    receivers:
    - name: 'default-receiver'
      email_configs:
      - to: 'y1486170457@qq.com'
        send_resolved: true
EOF

Alertmanager配置檔案解釋說明:

smtp_smarthost: 'smtp.163.com:25'
#用於傳送郵件的郵箱的SMTP伺服器地址+埠
smtp_from: '15011572657@163.com'
#這是指定從哪個郵箱傳送報警
smtp_auth_username: '15011572657'
#這是傳送郵箱的認證使用者，不是郵箱名
smtp_auth_password: 'BDBPRMLNZGKWRFJP'
#這是傳送郵箱的授權碼而不是登入密碼
email_configs:
   - to: 'y1486170457@qq.com'
#to後面指定傳送到哪個郵箱，我傳送到我的qq郵箱，大家需要寫自己的郵箱地址，不應該跟smtp_from的郵箱名字重複

在master節點重新生成prometheus-cfg.yaml檔案

kind: ConfigMap
apiVersion: v1
metadata:
  labels:
    app: prometheus
  name: prometheus-config
  namespace: monitor-sa
data:
  prometheus.yml: |
    rule_files:
    - /etc/prometheus/rules.yml
    alerting:
      alertmanagers:
      - static_configs:
        - targets: ["localhost:9093"]
    global:
      scrape_interval: 15s
      scrape_timeout: 10s
      evaluation_interval: 1m
    scrape_configs:
    - job_name: 'kubernetes-node'
      kubernetes_sd_configs:
      - role: node
      relabel_configs:
      - source_labels: [__address__]
        regex: '(.*):10250'
        replacement: '${1}:9100'
        target_label: __address__
        action: replace
      - action: labelmap
        regex: __meta_kubernetes_node_label_(.+)
    - job_name: 'kubernetes-node-cadvisor'
      kubernetes_sd_configs:
      - role:  node
      scheme: https
      tls_config:
        ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
      bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
      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
    - job_name: 'kubernetes-apiserver'
      kubernetes_sd_configs:
      - role: endpoints
      scheme: https
      tls_config:
        ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
      bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
      relabel_configs:
      - source_labels: [__meta_kubernetes_namespace, __meta_kubernetes_service_name, __meta_kubernetes_endpoint_port_name]
        action: keep
        regex: default;kubernetes;https
    - 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 
    - job_name: kubernetes-pods
      kubernetes_sd_configs:
      - role: pod
      relabel_configs:
      - action: keep
        regex: true
        source_labels:
        - __meta_kubernetes_pod_annotation_prometheus_io_scrape
      - action: replace
        regex: (.+)
        source_labels:
        - __meta_kubernetes_pod_annotation_prometheus_io_path
        target_label: __metrics_path__
      - action: replace
        regex: ([^:]+)(?::\d+)?;(\d+)
        replacement: $1:$2
        source_labels:
        - __address__
        - __meta_kubernetes_pod_annotation_prometheus_io_port
        target_label: __address__
      - action: labelmap
        regex: __meta_kubernetes_pod_label_(.+)
      - action: replace
        source_labels:
        - __meta_kubernetes_namespace
        target_label: kubernetes_namespace
      - action: replace
        source_labels:
        - __meta_kubernetes_pod_name
        target_label: kubernetes_pod_name
    - job_name: 'kubernetes-schedule'
      scrape_interval: 5s
      static_configs:
      - targets: ['172.16.9.3:10251']
    - job_name: 'kubernetes-controller-manager'
      scrape_interval: 5s
      static_configs:
      - targets: ['172.16.9.3:10252']
    - job_name: 'kubernetes-kube-proxy'
      scrape_interval: 5s
      static_configs:
      - targets: ['172.16.9.3:10249','172.16.9.4:10249']
    - job_name: 'kubernetes-etcd'
      scheme: https
      tls_config:
        ca_file: /var/run/secrets/kubernetes.io/k8s-certs/etcd/ca.crt
        cert_file: /var/run/secrets/kubernetes.io/k8s-certs/etcd/server.crt
        key_file: /var/run/secrets/kubernetes.io/k8s-certs/etcd/server.key
      scrape_interval: 5s
      static_configs:
      - targets: ['172.16.9.3:2379']
  rules.yml: |
    groups:
    - name: example
      rules:
      - alert: kube-proxy的cpu使用率大於80%
        expr: rate(process_cpu_seconds_total{job=~"kubernetes-kube-proxy"}[1m]) * 100 > 80
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}元件的cpu使用率超過80%"
      - alert:  kube-proxy的cpu使用率大於90%
        expr: rate(process_cpu_seconds_total{job=~"kubernetes-kube-proxy"}[1m]) * 100 > 90
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$lables.instance}}的{{$labels.job}}元件的cpu使用率超過90%"
      - alert: scheduler的cpu使用率大於80%
        expr: rate(process_cpu_seconds_total{job=~"kubernetes-schedule"}[1m]) * 100 > 80
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}元件的cpu使用率超過80%"
      - alert:  scheduler的cpu使用率大於90%
        expr: rate(process_cpu_seconds_total{job=~"kubernetes-schedule"}[1m]) * 100 > 90
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}元件的cpu使用率超過90%"
      - alert: controller-manager的cpu使用率大於80%
        expr: rate(process_cpu_seconds_total{job=~"kubernetes-controller-manager"}[1m]) * 100 > 80
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}元件的cpu使用率超過80%"
      - alert:  controller-manager的cpu使用率大於90%
        expr: rate(process_cpu_seconds_total{job=~"kubernetes-controller-manager"}[1m]) * 100 > 0
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}元件的cpu使用率超過90%"
      - alert: apiserver的cpu使用率大於80%
        expr: rate(process_cpu_seconds_total{job=~"kubernetes-apiserver"}[1m]) * 100 > 80
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}元件的cpu使用率超過80%"
      - alert:  apiserver的cpu使用率大於90%
        expr: rate(process_cpu_seconds_total{job=~"kubernetes-apiserver"}[1m]) * 100 > 90
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}元件的cpu使用率超過90%"
      - alert: etcd的cpu使用率大於80%
        expr: rate(process_cpu_seconds_total{job=~"kubernetes-etcd"}[1m]) * 100 > 80
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}元件的cpu使用率超過80%"
      - alert:  etcd的cpu使用率大於90%
        expr: rate(process_cpu_seconds_total{job=~"kubernetes-etcd"}[1m]) * 100 > 90
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}元件的cpu使用率超過90%"
      - alert: kube-state-metrics的cpu使用率大於80%
        expr: rate(process_cpu_seconds_total{k8s_app=~"kube-state-metrics"}[1m]) * 100 > 80
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.k8s_app}}元件的cpu使用率超過80%"
          value: "{{ $value }}%"
          threshold: "80%"      
      - alert: kube-state-metrics的cpu使用率大於90%
        expr: rate(process_cpu_seconds_total{k8s_app=~"kube-state-metrics"}[1m]) * 100 > 0
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.k8s_app}}元件的cpu使用率超過90%"
          value: "{{ $value }}%"
          threshold: "90%"      
      - alert: coredns的cpu使用率大於80%
        expr: rate(process_cpu_seconds_total{k8s_app=~"kube-dns"}[1m]) * 100 > 80
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.k8s_app}}元件的cpu使用率超過80%"
          value: "{{ $value }}%"
          threshold: "80%"      
      - alert: coredns的cpu使用率大於90%
        expr: rate(process_cpu_seconds_total{k8s_app=~"kube-dns"}[1m]) * 100 > 90
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.k8s_app}}元件的cpu使用率超過90%"
          value: "{{ $value }}%"
          threshold: "90%"      
      - alert: kube-proxy開啟控制程式碼數>600
        expr: process_open_fds{job=~"kubernetes-kube-proxy"}  > 600
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}開啟控制程式碼數>600"
          value: "{{ $value }}"
      - alert: kube-proxy開啟控制程式碼數>1000
        expr: process_open_fds{job=~"kubernetes-kube-proxy"}  > 1000
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}開啟控制程式碼數>1000"
          value: "{{ $value }}"
      - alert: kubernetes-schedule開啟控制程式碼數>600
        expr: process_open_fds{job=~"kubernetes-schedule"}  > 600
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}開啟控制程式碼數>600"
          value: "{{ $value }}"
      - alert: kubernetes-schedule開啟控制程式碼數>1000
        expr: process_open_fds{job=~"kubernetes-schedule"}  > 1000
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}開啟控制程式碼數>1000"
          value: "{{ $value }}"
      - alert: kubernetes-controller-manager開啟控制程式碼數>600
        expr: process_open_fds{job=~"kubernetes-controller-manager"}  > 600
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}開啟控制程式碼數>600"
          value: "{{ $value }}"
      - alert: kubernetes-controller-manager開啟控制程式碼數>1000
        expr: process_open_fds{job=~"kubernetes-controller-manager"}  > 1000
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}開啟控制程式碼數>1000"
          value: "{{ $value }}"
      - alert: kubernetes-apiserver開啟控制程式碼數>600
        expr: process_open_fds{job=~"kubernetes-apiserver"}  > 600
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}開啟控制程式碼數>600"
          value: "{{ $value }}"
      - alert: kubernetes-apiserver開啟控制程式碼數>1000
        expr: process_open_fds{job=~"kubernetes-apiserver"}  > 1000
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}開啟控制程式碼數>1000"
          value: "{{ $value }}"
      - alert: kubernetes-etcd開啟控制程式碼數>600
        expr: process_open_fds{job=~"kubernetes-etcd"}  > 600
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}開啟控制程式碼數>600"
          value: "{{ $value }}"
      - alert: kubernetes-etcd開啟控制程式碼數>1000
        expr: process_open_fds{job=~"kubernetes-etcd"}  > 1000
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "{{$labels.instance}}的{{$labels.job}}開啟控制程式碼數>1000"
          value: "{{ $value }}"
      - alert: coredns
        expr: process_open_fds{k8s_app=~"kube-dns"}  > 600
        for: 2s
        labels:
          severity: warnning 
        annotations:
          description: "外掛{{$labels.k8s_app}}({{$labels.instance}}): 開啟控制程式碼數超過600"
          value: "{{ $value }}"
      - alert: coredns
        expr: process_open_fds{k8s_app=~"kube-dns"}  > 1000
        for: 2s
        labels:
          severity: critical
        annotations:
          description: "外掛{{$labels.k8s_app}}({{$labels.instance}}): 開啟控制程式碼數超過1000"
          value: "{{ $value }}"
      - alert: kube-proxy
        expr: process_virtual_memory_bytes{job=~"kubernetes-kube-proxy"}  > 2000000000
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "元件{{$labels.job}}({{$labels.instance}}): 使用虛擬記憶體超過2G"
          value: "{{ $value }}"
      - alert: scheduler
        expr: process_virtual_memory_bytes{job=~"kubernetes-schedule"}  > 2000000000
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "元件{{$labels.job}}({{$labels.instance}}): 使用虛擬記憶體超過2G"
          value: "{{ $value }}"
      - alert: kubernetes-controller-manager
        expr: process_virtual_memory_bytes{job=~"kubernetes-controller-manager"}  > 2000000000
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "元件{{$labels.job}}({{$labels.instance}}): 使用虛擬記憶體超過2G"
          value: "{{ $value }}"
      - alert: kubernetes-apiserver
        expr: process_virtual_memory_bytes{job=~"kubernetes-apiserver"}  > 2000000000
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "元件{{$labels.job}}({{$labels.instance}}): 使用虛擬記憶體超過2G"
          value: "{{ $value }}"
      - alert: kubernetes-etcd
        expr: process_virtual_memory_bytes{job=~"kubernetes-etcd"}  > 2000000000
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "元件{{$labels.job}}({{$labels.instance}}): 使用虛擬記憶體超過2G"
          value: "{{ $value }}"
      - alert: kube-dns
        expr: process_virtual_memory_bytes{k8s_app=~"kube-dns"}  > 2000000000
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "外掛{{$labels.k8s_app}}({{$labels.instance}}): 使用虛擬記憶體超過2G"
          value: "{{ $value }}"
      - alert: HttpRequestsAvg
        expr: sum(rate(rest_client_requests_total{job=~"kubernetes-kube-proxy|kubernetes-kubelet|kubernetes-schedule|kubernetes-control-manager|kubernetes-apiservers"}[1m]))  > 1000
        for: 2s
        labels:
          team: admin
        annotations:
          description: "元件{{$labels.job}}({{$labels.instance}}): TPS超過1000"
          value: "{{ $value }}"
          threshold: "1000"   
      - alert: Pod_restarts
        expr: kube_pod_container_status_restarts_total{namespace=~"kube-system|default|monitor-sa"} > 0
        for: 2s
        labels:
          severity: warnning
        annotations:
          description: "在{{$labels.namespace}}名稱空間下發現{{$labels.pod}}這個pod下的容器{{$labels.container}}被重啟,這個監控指標是由{{$labels.instance}}採集的"
          value: "{{ $value }}"
          threshold: "0"
      - alert: Pod_waiting
        expr: kube_pod_container_status_waiting_reason{namespace=~"kube-system|default"} == 1
        for: 2s
        labels:
          team: admin
        annotations:
          description: "空間{{$labels.namespace}}({{$labels.instance}}): 發現{{$labels.pod}}下的{{$labels.container}}啟動異常等待中"
          value: "{{ $value }}"
          threshold: "1"   
      - alert: Pod_terminated
        expr: kube_pod_container_status_terminated_reason{namespace=~"kube-system|default|monitor-sa"} == 1
        for: 2s
        labels:
          team: admin
        annotations:
          description: "空間{{$labels.namespace}}({{$labels.instance}}): 發現{{$labels.pod}}下的{{$labels.container}}被刪除"
          value: "{{ $value }}"
          threshold: "1"
      - alert: Etcd_leader
        expr: etcd_server_has_leader{job="kubernetes-etcd"} == 0
        for: 2s
        labels:
          team: admin
        annotations:
          description: "元件{{$labels.job}}({{$labels.instance}}): 當前沒有leader"
          value: "{{ $value }}"
          threshold: "0"
      - alert: Etcd_leader_changes
        expr: rate(etcd_server_leader_changes_seen_total{job="kubernetes-etcd"}[1m]) > 0
        for: 2s
        labels:
          team: admin
        annotations:
          description: "元件{{$labels.job}}({{$labels.instance}}): 當前leader已發生改變"
          value: "{{ $value }}"
          threshold: "0"
      - alert: Etcd_failed
        expr: rate(etcd_server_proposals_failed_total{job="kubernetes-etcd"}[1m]) > 0
        for: 2s
        labels:
          team: admin
        annotations:
          description: "元件{{$labels.job}}({{$labels.instance}}): 服務失敗"
          value: "{{ $value }}"
          threshold: "0"
      - alert: Etcd_db_total_size
        expr: etcd_debugging_mvcc_db_total_size_in_bytes{job="kubernetes-etcd"} > 10000000000
        for: 2s
        labels:
          team: admin
        annotations:
          description: "元件{{$labels.job}}({{$labels.instance}})：db空間超過10G"
          value: "{{ $value }}"
          threshold: "10G"
      - alert: Endpoint_ready
        expr: kube_endpoint_address_not_ready{namespace=~"kube-system|default"} == 1
        for: 2s
        labels:
          team: admin
        annotations:
          description: "空間{{$labels.namespace}}({{$labels.instance}}): 發現{{$labels.endpoint}}不可用"
          value: "{{ $value }}"
          threshold: "1"
    - name: 物理節點狀態-監控告警
      rules:
      - alert: 物理節點cpu使用率
        expr: 100-avg(irate(node_cpu_seconds_total{mode="idle"}[5m])) by(instance)*100 > 90
        for: 2s
        labels:
          severity: ccritical
        annotations:
          summary: "{{ $labels.instance }}cpu使用率過高"
          description: "{{ $labels.instance }}的cpu使用率超過90%,當前使用率[{{ $value }}],需要排查處理" 
      - alert: 物理節點記憶體使用率
        expr: (node_memory_MemTotal_bytes - (node_memory_MemFree_bytes + node_memory_Buffers_bytes + node_memory_Cached_bytes)) / node_memory_MemTotal_bytes * 100 > 90
        for: 2s
        labels:
          severity: critical
        annotations:
          summary: "{{ $labels.instance }}記憶體使用率過高"
          description: "{{ $labels.instance }}的記憶體使用率超過90%,當前使用率[{{ $value }}],需要排查處理"
      - alert: InstanceDown
        expr: up == 0
        for: 2s
        labels:
          severity: critical
        annotations:   
          summary: "{{ $labels.instance }}: 伺服器當機"
          description: "{{ $labels.instance }}: 伺服器延時超過2分鐘"
      - alert: 物理節點磁碟的IO效能
        expr: 100-(avg(irate(node_disk_io_time_seconds_total[1m])) by(instance)* 100) < 60
        for: 2s
        labels:
          severity: critical
        annotations:
          summary: "{{$labels.mountpoint}} 流入磁碟IO使用率過高！"
          description: "{{$labels.mountpoint }} 流入磁碟IO大於60%(目前使用:{{$value}})"
      - alert: 入網流量頻寬
        expr: ((sum(rate (node_network_receive_bytes_total{device!~'tap.*|veth.*|br.*|docker.*|virbr*|lo*'}[5m])) by (instance)) / 100) > 102400
        for: 2s
        labels:
          severity: critical
        annotations:
          summary: "{{$labels.mountpoint}} 流入網路頻寬過高！"
          description: "{{$labels.mountpoint }}流入網路頻寬持續5分鐘高於100M. RX頻寬使用率{{$value}}"
      - alert: 出網流量頻寬
        expr: ((sum(rate (node_network_transmit_bytes_total{device!~'tap.*|veth.*|br.*|docker.*|virbr*|lo*'}[5m])) by (instance)) / 100) > 102400
        for: 2s
        labels:
          severity: critical
        annotations:
          summary: "{{$labels.mountpoint}} 流出網路頻寬過高！"
          description: "{{$labels.mountpoint }}流出網路頻寬持續5分鐘高於100M. RX頻寬使用率{{$value}}"
      - alert: TCP會話
        expr: node_netstat_Tcp_CurrEstab > 1000
        for: 2s
        labels:
          severity: critical
        annotations:
          summary: "{{$labels.mountpoint}} TCP_ESTABLISHED過高！"
          description: "{{$labels.mountpoint }} TCP_ESTABLISHED大於1000%(目前使用:{{$value}}%)"
      - alert: 磁碟容量
        expr: 100-(node_filesystem_free_bytes{fstype=~"ext4|xfs"}/node_filesystem_size_bytes {fstype=~"ext4|xfs"}*100) > 80
        for: 2s
        labels:
          severity: critical
        annotations:
          summary: "{{$labels.mountpoint}} 磁碟分割槽使用率過高！"
          description: "{{$labels.mountpoint }} 磁碟分割槽使用大於80%(目前使用:{{$value}}%)"

同樣需要手動新增$的變數。

在k8smaster節點重新生成一個prometheus-deploy.yaml檔案

cat >prometheus-deploy.yaml <<EOF
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: prometheus-server
  namespace: monitor-sa
  labels:
    app: prometheus
spec:
  replicas: 1
  selector:
    matchLabels:
      app: prometheus
      component: server
    #matchExpressions:
    #- {key: app, operator: In, values: [prometheus]}
    #- {key: component, operator: In, values: [server]}
  template:
    metadata:
      labels:
        app: prometheus
        component: server
      annotations:
        prometheus.io/scrape: 'false'
    spec:
      nodeName: node1
      serviceAccountName: monitor
      containers:
      - name: prometheus
        image: prom/prometheus:v2.2.1
        imagePullPolicy: IfNotPresent
        command:
        - "/bin/prometheus"
        args:
        - "--config.file=/etc/prometheus/prometheus.yml"
        - "--storage.tsdb.path=/prometheus"
        - "--storage.tsdb.retention=24h"
        - "--web.enable-lifecycle"
        ports:
        - containerPort: 9090
          protocol: TCP
        volumeMounts:
        - mountPath: /etc/prometheus
          name: prometheus-config
        - mountPath: /prometheus/
          name: prometheus-storage-volume
        - name: k8s-certs
          mountPath: /var/run/secrets/kubernetes.io/k8s-certs/etcd/
      - name: alertmanager
        image: prom/alertmanager:v0.14.0
        imagePullPolicy: IfNotPresent
        args:
        - "--config.file=/etc/alertmanager/alertmanager.yml"
        - "--log.level=debug"
        ports:
        - containerPort: 9093
          protocol: TCP
          name: alertmanager
        volumeMounts:
        - name: alertmanager-config
          mountPath: /etc/alertmanager
        - name: alertmanager-storage
          mountPath: /alertmanager
        - name: localtime
          mountPath: /etc/localtime
      volumes:
        - name: prometheus-config
          configMap:
            name: prometheus-config
        - name: prometheus-storage-volume
          hostPath:
           path: /data
           type: Directory
        - name: k8s-certs
          secret:
           secretName: etcd-certs
        - name: alertmanager-config
          configMap:
            name: alertmanager
        - name: alertmanager-storage
          hostPath:
           path: /data/alertmanager
           type: DirectoryOrCreate
        - name: localtime
          hostPath:
           path: /usr/share/zoneinfo/Asia/Shanghai
EOF

生成一個etch-certs，這個在部署prometheus需要

kubectl -n monitor-sa create secret generic etcd-certs --from-file=/etc/kubernetes/pki/etcd/server.key  --from-file=/etc/kubernetes/pki/etcd/server.crt --from-file=/etc/kubernetes/pki/etcd/ca.crt

更新yaml檔案，檢視部署是否成功。

在k8smaster節點上重新生成一個alertmanager-svc.yaml檔案

cat >alertmanager-svc.yaml <<EOF
---
apiVersion: v1
kind: Service
metadata:
  labels:
    name: prometheus
    kubernetes.io/cluster-service: 'true'
  name: alertmanager
  namespace: monitor-sa
spec:
  ports:
  - name: alertmanager
    nodePort: 30066
    port: 9093
    protocol: TCP
    targetPort: 9093
  selector:
    app: prometheus
  sessionAffinity: None
  type: NodePort
EOF

#檢視service在物理機對映的埠

kubectl get svc -n monitor-sa

訪問prometheus介面，點選alerts，把controller-manager的cpu使用率大於90%展開，可看到status為FIRING，表示prometheus已經將告警發給alertmanager，在Alertmanager 中可以看到有一個 alert。

登入alertmanager web介面檢視

配置alertmanager報警-傳送報警到釘釘

建立釘釘機器人

開啟電腦版釘釘，建立一個群，建立自定義機器人，按如下步驟建立
https://ding-doc.dingtalk.com/doc#/serverapi2/qf2nxq

我建立的機器人如下：
群設定-->智慧群助手-->新增機器人-->自定義-->新增

機器人名稱：kube-event
接收群組：釘釘報警測試

安全設定：
自定義關鍵詞：cluster1

上面配置好之後點選完成即可，這樣就會建立一個kube-event的報警機器人，建立機器人成功之後怎麼檢視webhook，按如下：

點選智慧群助手，可以看到剛才建立的kube-event這個機器人，點選kube-event，就會進入到kube-event機器人的設定介面
出現如下內容：
機器人名稱：kube-event
接受群組：釘釘報警測試
訊息推送：開啟
webhook：https://oapi.dingtalk.com/robot/send?access_token=9c03ff1f47b1d15a10d852398cafb84f8e81ceeb1ba557eddd8a79e5a5e5548e
安全設定：
自定義關鍵詞：cluster1

安裝釘釘的webhook外掛，在master節點操作

tar zxvf prometheus-webhook-dingtalk-0.3.0.linux-amd64.tar.gz
#壓縮包地址
#連結：https://pan.baidu.com/s/1_HtVZsItq2KsYvOlkIP9DQ 
#提取碼：d59o
cd prometheus-webhook-dingtalk-0.3.0.linux-amd64

#啟動釘釘報警外掛
nohup ./prometheus-webhook-dingtalk --web.listen-address="0.0.0.0:8060" --ding.profile="cluster1=https://oapi.dingtalk.com/robot/send?access_token=4372b6419ff1f198a9732dfb9f469f8c7eb7310dec00ede726a7ecd9d235c9b9" &

#對原來的檔案做備份
cp alertmanager-cm.yaml alertmanager-cm.yaml.bak

#重新生成一個新的alertmanager-cm.yaml檔案
cat >alertmanager-cm.yaml <<EOF
kind: ConfigMap
apiVersion: v1
metadata:
  name: alertmanager
  namespace: monitor-sa
data:
  alertmanager.yml: |-
    global:
      resolve_timeout: 1m
      smtp_smarthost: 'smtp.163.com:25'
      smtp_from: '15011572657@163.com'
      smtp_auth_username: '15011572657'
      smtp_auth_password: 'BDBPRMLNZGKWRFJP'
      smtp_require_tls: false
    route:
      group_by: [alertname]
      group_wait: 10s
      group_interval: 10s
      repeat_interval: 10m
      receiver: cluster1
    receivers:
    - name: cluster1
      webhook_configs:
      - url: 'http://192.168.124.16:8060/dingtalk/cluster1/send'
        send_resolved: true
EOF

#通過kubectl apply使配置生效
kubectl delete -f alertmanager-cm.yaml
kubectl  apply  -f alertmanager-cm.yaml
kubectl delete -f prometheus-cfg.yaml
kubectl apply  -f prometheus-cfg.yaml
kubectl delete  -f prometheus-deploy.yaml
kubectl apply  -f  prometheus-deploy.yaml
#通過上面步驟，就可以實現釘釘報警了

參考連結：https://mp.weixin.qq.com/s/I1-xfxuny_S8DHchkXHSpQ

監控系統告警指令碼集合
2021-05-08
指令碼
告警系統主指令碼、告警系統配置檔案、告警系統監控專案
2017-11-15
指令碼
【系統設計】指標監控和告警系統
2022-07-05
指標
運維文件：系統監控及告警配置
2024-07-26
運維
細說夜鶯監控系統告警自愈機制
2024-05-08
python搭建系統監控
2018-09-26
Python
Nagios監控系統搭建
2015-03-15
iOS
搭建完美的監控系統
2012-12-20
基於 Prometheus+Grafana+Alertmanager 搭建 K8S 雲監控告警平臺（附配置告警至QQ、釘釘）
2024-10-07
PrometheusGrafanaK8S
分散式系統關注點(22)——360°的全方位監控
2019-07-02
分散式
前端監控系統Sentry搭建
2020-04-03
前端
搭建前端錯誤監控系統
2018-11-29
前端
轉轉支付通道監控系統的搭建
2023-04-26
prometheus監控+alertmanager告警
2024-03-07
Prometheus
前端監控基礎篇 — Docker + Sentry 搭建前端監控系統
2020-02-15
前端Docker
分散式監控系統Zabbix3.4-釘釘告警配置記錄
2018-09-03
分散式
雲監控告警2.0：革新傳統告警機制，引領智慧化監控新時代
2024-03-14
多雲監控告警系統的優勢
2023-02-03
JavaWeb的監控系統
2016-07-21
JavaWeb
Zabbix如何監控Oracle的告警日誌
2024-09-21
Oracle
安防監控影片匯聚系統EasyCVR平臺如何接入EHOME告警？
2024-03-21
VR
grafana+prometheus快速搭建MySql監控系統實踐
2018-08-15
GrafanaPrometheusMySql
docker-compose 搭建 Prometheus+Grafana監控系統
2022-06-12
DockerPrometheusGrafana
搭建一個前端監控系統,不再錯過BUG
2017-12-18
前端
Mysql 監控系統
2009-02-05
MySql
監控系統元件
2011-10-09
元件
能源管控系統開發解決方案,線上監測系統搭建
2019-12-03
運維監控系統 PIGOSS BSM的監控策略
2017-11-22
運維Go
實時監控系統，統一監控企業API
2022-03-10
API
docker-compose快速搭建 Prometheus+Grafana監控系統
2019-03-29
DockerPrometheusGrafana
能耗線上管理平臺搭建能源監控系統開發
2019-04-03
智慧警務視覺化應用監控系統搭建
2020-12-01
視覺化
搭建服務端效能監控系統 Prometheus 詳細指南
2024-06-19
服務端Prometheus
prometheus之docker監控與告警系列（一）
2018-09-14
PrometheusDocker
prometheus之docker監控與告警系列（二）
2018-09-14
PrometheusDocker
prometheus之docker監控與告警系列（三）
2018-09-14
PrometheusDocker
歸檔告警頻繁監控指令碼
2015-08-11
指令碼
Mac系統監控工具
2020-06-10
Mac