当前位置: 首页 > news >正文

k8s---prometheus 监控

目录

环境准备

        下载 kube-prometheus 软件包

        下载prometheus 镜像

master节点

master节点导入prometheus软件包

解压

node节点

node节点导入镜像

解压

从tar包中加载镜像

部署 prometheus

修改映射端口

提交

查看pod

pod和svc正常启动

deployment

daemonset

service

删除影响外部访问的pod资源

网页访问


环境准备

        下载 kube-prometheus 软件包
        下载prometheus 镜像

master节点

master节点导入prometheus软件包
[root@k8s-master ~]# mkdir prometheus
[root@k8s-master ~]# cd prometheus/
[root@k8s-master prometheus]# ls
kube-prometheus-0.13.0.zip
解压
[root@k8s-master prometheus]# unzip kube-prometheus-0.13.0.zip 
Archive:  kube-prometheus-0.13.0.zip

node节点

node节点导入镜像
[root@k8s-node1 ~]# mkdir prometheus
[root@k8s-node1 ~]# cd prometheus/
[root@k8s-node1 prometheus]# rz
rz waiting to receive.**[root@k8s-node1 prometheus]# ls
prometheus.zip
解压
[root@k8s-node1 prometheus]# unzip prometheus.zip 
Archive:  prometheus.zipinflating: prometheus.tar   
从tar包中加载镜像
[root@k8s-node1 prometheus]# ls
prometheus.tar  prometheus.zip
[root@k8s-node1 prometheus]# docker load -i prometheus.tar 

部署 prometheus

修改映射端口
[root@k8s-master manifests]# vim prometheus-service.yaml 
[root@k8s-master manifests]# vim grafana-service.yaml
[root@k8s-master manifests]# vim alertmanager-service.yaml 

以上配置文件分别增加如下配置:

spec:type: NodePort

提交
kubectl create -f ./setup
kubectl create -f ./
查看pod
pod和svc正常启动
[root@k8s-master manifests]# kubectl -n monitoring get po
NAME                                   READY   STATUS    RESTARTS   AGE
alertmanager-main-0                    2/2     Running   0          63s
alertmanager-main-1                    2/2     Running   0          63s
alertmanager-main-2                    2/2     Running   0          63s
blackbox-exporter-6cfc4bffb6-jwxzx     3/3     Running   0          66s
grafana-748964b847-5drhv               1/1     Running   0          65s
kube-state-metrics-6b4d48dcb4-9wzdr    3/3     Running   0          65s
node-exporter-2g9b5                    2/2     Running   0          65s
node-exporter-fn86k                    2/2     Running   0          65s
node-exporter-pl4xk                    2/2     Running   0          65s
prometheus-adapter-79c588b474-gfjn5    1/1     Running   0          64s
prometheus-adapter-79c588b474-ncx2m    1/1     Running   0          64s
prometheus-k8s-0                       2/2     Running   0          63s
prometheus-k8s-1                       2/2     Running   0          63s
prometheus-operator-68f6c79f9d-jmm6r   2/2     Running   0          64s

deployment
[root@k8s-master manifests]# kubectl -n monitoring get deployments.apps 
NAME                  READY   UP-TO-DATE   AVAILABLE   AGE
blackbox-exporter     1/1     1            1           2m13s
grafana               1/1     1            1           2m13s
kube-state-metrics    1/1     1            1           2m12s
prometheus-adapter    2/2     2            2           2m12s
prometheus-operator   1/1     1            1           2m11s

daemonset
[root@k8s-master manifests]# kubectl -n monitoring get daemonsets.apps 
NAME            DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
node-exporter   3         3         3       3            3           kubernetes.io/os=linux   2m44s

service
[root@k8s-master manifests]# kubectl -n monitoring get svc
NAME                    TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                         AGE
alertmanager-main       NodePort    10.103.129.205   <none>        9093:30620/TCP,8080:31461/TCP   2m22s
alertmanager-operated   ClusterIP   None             <none>        9093/TCP,9094/TCP,9094/UDP      2m19s
blackbox-exporter       ClusterIP   10.96.163.18     <none>        9115/TCP,19115/TCP              2m22s
grafana                 NodePort    10.100.242.32    <none>        3000:31046/TCP                  2m21s
kube-state-metrics      ClusterIP   None             <none>        8443/TCP,9443/TCP               2m21s
node-exporter           ClusterIP   None             <none>        9100/TCP                        2m21s
prometheus-adapter      ClusterIP   10.104.32.247    <none>        443/TCP                         2m21s
prometheus-k8s          NodePort    10.109.128.29    <none>        9090:32732/TCP,8080:30519/TCP   2m21s
prometheus-operated     ClusterIP   None             <none>        9090/TCP                        2m19s
prometheus-operator     ClusterIP   None             <none>        8443/TCP                        2m20s

删除影响外部访问的pod资源

[root@k8s-master manifests]# kubectl delete -f prometheus-networkPolicy.yaml
networkpolicy.networking.k8s.io "prometheus-k8s" deleted
[root@k8s-master manifests]# kubectl delete -f grafana-networkPolicy.yaml
networkpolicy.networking.k8s.io "grafana" deleted
[root@k8s-master manifests]# kubectl delete -f alertmanager-networkPolicy.yaml
networkpolicy.networking.k8s.io "alertmanager-main" deleted

网页访问

a

192.168.158.33:31046

#访问用户和密码

admin/admin

prometheus就是通过内部端口9090进行访问的

如何设置告警信息呢?

如下操作:

进到prometheus-k8s-0  容器里

[root@k8s-master manifests]# kubectl -n monitoring get po
NAME                                   READY   STATUS    RESTARTS   AGE
alertmanager-main-0                    2/2     Running   0          3h49m
alertmanager-main-1                    2/2     Running   0          3h49m
alertmanager-main-2                    2/2     Running   0          3h49m
blackbox-exporter-6cfc4bffb6-jwxzx     3/3     Running   0          3h49m
grafana-bc647458d-rnrcj                1/1     Running   0          3h28m
kube-state-metrics-6b4d48dcb4-9wzdr    3/3     Running   0          3h49m
node-exporter-2g9b5                    2/2     Running   0          3h49m
node-exporter-fn86k                    2/2     Running   0          3h49m
node-exporter-pl4xk                    2/2     Running   0          3h49m
prometheus-adapter-79c588b474-gfjn5    1/1     Running   0          3h49m
prometheus-adapter-79c588b474-ncx2m    1/1     Running   0          3h49m
prometheus-k8s-0                       2/2     Running   0          3h49m
prometheus-k8s-1                       2/2     Running   0          3h49m
prometheus-operator-68f6c79f9d-jmm6r   2/2     Running   0          3h49m

[root@k8s-master manifests]# kubectl -n monitoring exec -it prometheus-k8s-0 -- sh
/prometheus $ 
/prometheus $ cd 

主要文件:prometheus.yml 
告警规则:rules

打开          # - alertmanager:9093

http://www.dtcms.com/a/360178.html

相关文章:

  • AI大模型实战解析-RAG知识库+LangChain项目实战
  • 《SVA断言系统学习之路》【01】即时断言概览
  • IDM(Internet Download Managerv 6.38)破除解版下载!IDM 下载器永久免费版!提升下载速度达5倍!安装及使用
  • 深入解析Linux系统中的/etc/hosts文件
  • 刷题日记0831
  • 盲孔轴旋转编码器轴设计与加工的几个注意事项
  • 网络爬虫是自动从互联网上采集数据的程序
  • 开源知识抽取框架 推荐
  • Python基础之元组列表集合字典
  • 数据化管理是什么意思?企业该如何进行数据化管理
  • 介绍GSPO:一种革命性的语言模型强化学习算法
  • 【系统分析师】高分论文:论信息系统的安全与保密设计
  • 利用爬虫获取淘宝商品信息,参数解析
  • 大语言模型(LLM)简介与应用分享
  • Linux 系统忘记 root 密码?紧急救援方案与原理详解
  • 【STM32】外部中断(下)
  • kkfile一键部署-ubuntu版
  • Transformer中的核心概念III-Attention
  • 江协示例3.1LED闪烁,下载程序后要复位LED才点亮的设置。
  • 随时随地开发:通过 FRP 搭建从 Ubuntu 到 Windows 的远程 Android 调试环境
  • leetcode_48 旋转图像
  • DAY50打卡
  • Ansible配置文件与主机清单
  • Library cache lock常见案例分析(二)
  • 在Windows的wsl中如何以root登录Ubuntu
  • KMP 算法相关练习题
  • AI 重构内容创作:从文案生成到视频剪辑,创作者该如何与 AI 协同共生?
  • 用产品经理的思维,重构AI时代的增长Playbook
  • CatBoost vs XGBoost:两大Boosting框架的全面对比
  • 【AI智能体】Dify 实现自然语言转SQL操作数据库实战详解