``>  @创建部署问题时,请参考下面模板,你提供的信息越多,越容易及时获得解答。

你只花一分钟创建的问题,不能指望别人花上半个小时给你解答。
发帖前请点击 发表主题 右边的 预览(👀) 按钮,确保帖子格式正确。

操作系统信息
虚拟机,Centos9,4C/8G

Kubernetes版本信息
v1.27.5,五节点。

容器运行时
dcontainerd

KubeSphere版本信息
例如:v3.4.1。在线安装。已有K8s安装还是全套安装。

问题是什么
需求是这样,将现有kubesphere的普罗加入blackbox监控

1、部署监控服务后,打开普罗的web页面,只找到blackbox的servermonitor 定义的probe规则没发现

[root@host-192-168-2-31 manifests]# kubectl get probes.monitoring.coreos.com  -A

NAMESPACE                      NAME         AGE

kubesphere-monitoring-system   icmp-probe   30h

kubesphere-monitoring-system   ping         24h

kubesphere-monitoring-system   test-probe   25h

kubesphere-monitoring-system   test-probe   25h
[root@host-192-168-2-31 manifests]# kubectl get pod -A
NAMESPACE                      NAME                                               READY   STATUS      RESTARTS       AGE
kube-system                    calico-kube-controllers-df694455f-s8pqh            1/1     Running     6 (74m ago)    34h
kube-system                    calico-node-746jr                                  1/1     Running     6 (74m ago)    34h
kube-system                    calico-node-hfcdz                                  1/1     Running     6 (74m ago)    34h
kube-system                    calico-node-sftt4                                  1/1     Running     6 (74m ago)    34h
kube-system                    calico-node-tdgcp                                  1/1     Running     6 (74m ago)    34h
kube-system                    calico-node-w4cvm                                  1/1     Running     6 (74m ago)    34h
kube-system                    coredns-5858d8bb58-hdvnw                           1/1     Running     6 (74m ago)    34h
kube-system                    coredns-5858d8bb58-j49zp                           1/1     Running     6 (74m ago)    34h
kube-system                    haproxy-host-192-168-2-34                          1/1     Running     6 (74m ago)    34h
kube-system                    haproxy-host-192-168-2-35                          1/1     Running     6 (74m ago)    34h
kube-system                    kube-apiserver-host-192-168-2-31                   1/1     Running     6 (74m ago)    34h
kube-system                    kube-apiserver-host-192-168-2-32                   1/1     Running     6 (74m ago)    34h
kube-system                    kube-apiserver-host-192-168-2-33                   1/1     Running     6 (74m ago)    34h
kube-system                    kube-controller-manager-host-192-168-2-31          1/1     Running     7 (74m ago)    34h
kube-system                    kube-controller-manager-host-192-168-2-32          1/1     Running     6 (74m ago)    34h
kube-system                    kube-controller-manager-host-192-168-2-33          1/1     Running     7 (74m ago)    34h
kube-system                    kube-proxy-6qcr6                                   1/1     Running     6 (74m ago)    34h
kube-system                    kube-proxy-dsqg5                                   1/1     Running     6 (74m ago)    34h
kube-system                    kube-proxy-nqwmc                                   1/1     Running     6 (74m ago)    34h
kube-system                    kube-proxy-z6bz5                                   1/1     Running     6 (74m ago)    34h
kube-system                    kube-proxy-zpkqk                                   1/1     Running     6 (74m ago)    34h
kube-system                    kube-scheduler-host-192-168-2-31                   1/1     Running     7 (74m ago)    34h
kube-system                    kube-scheduler-host-192-168-2-32                   1/1     Running     6 (74m ago)    34h
kube-system                    kube-scheduler-host-192-168-2-33                   1/1     Running     6 (74m ago)    34h
kube-system                    metrics-server-66549d4ff5-jh5lh                    1/1     Running     10 (73m ago)   34h
kube-system                    nodelocaldns-5mc5n                                 1/1     Running     6 (74m ago)    34h
kube-system                    nodelocaldns-76lgl                                 1/1     Running     6 (74m ago)    34h
kube-system                    nodelocaldns-9t4h5                                 1/1     Running     6 (74m ago)    34h
kube-system                    nodelocaldns-m9n4c                                 1/1     Running     6 (74m ago)    34h
kube-system                    nodelocaldns-zqflm                                 1/1     Running     6 (74m ago)    34h
kube-system                    openebs-localpv-provisioner-55bdd4b6c7-4hknj       1/1     Running     8 (72m ago)    34h
kube-system                    snapshot-controller-0                              1/1     Running     6 (74m ago)    34h
kubesphere-controls-system     default-http-backend-bb44579cb-gfwqj               1/1     Running     6 (74m ago)    34h
kubesphere-controls-system     kubectl-admin-685dbc7f7b-rr8xk                     1/1     Running     6 (74m ago)    34h
kubesphere-monitoring-system   alertmanager-main-0                                2/2     Running     12 (74m ago)   34h
kubesphere-monitoring-system   alertmanager-main-1                                2/2     Running     12 (74m ago)   34h
kubesphere-monitoring-system   alertmanager-main-2                                2/2     Running     12 (74m ago)   34h
kubesphere-monitoring-system   blackbox-exporter-7fd74696c9-fvc8x                 3/3     Running     6 (74m ago)    25h
kubesphere-monitoring-system   kube-state-metrics-7db6ccf9d6-wbkkb                3/3     Running     19 (74m ago)   34h
kubesphere-monitoring-system   node-exporter-b8xr4                                2/2     Running     12 (74m ago)   34h
kubesphere-monitoring-system   node-exporter-hpplz                                2/2     Running     12 (74m ago)   34h
kubesphere-monitoring-system   node-exporter-mjkcg                                2/2     Running     12 (74m ago)   34h
kubesphere-monitoring-system   node-exporter-xqvfd                                2/2     Running     12 (74m ago)   34h
kubesphere-monitoring-system   node-exporter-xx4sc                                2/2     Running     12 (74m ago)   34h
kubesphere-monitoring-system   notification-manager-deployment-56dbc56444-8qxg8   2/2     Running     17 (73m ago)   34h
kubesphere-monitoring-system   notification-manager-deployment-56dbc56444-ktnq4   2/2     Running     18 (72m ago)   34h
kubesphere-monitoring-system   notification-manager-operator-dbb677dd9-6b58w      2/2     Running     13 (74m ago)   34h
kubesphere-monitoring-system   prometheus-k8s-0                                   2/2     Running     0              41m
kubesphere-monitoring-system   prometheus-k8s-1                                   2/2     Running     0              41m
kubesphere-monitoring-system   prometheus-operator-697974d674-mq74f               2/2     Running     0              41m
kubesphere-monitoring-system   thanos-ruler-kubesphere-0                          2/2     Running     21 (73m ago)   34h
kubesphere-monitoring-system   thanos-ruler-kubesphere-1                          2/2     Running     19 (73m ago)   34h
kubesphere-system              ks-apiserver-7f96c68555-x9kgk                      1/1     Running     6 (74m ago)    34h
kubesphere-system              ks-console-5849989f6-s62ln                         1/1     Running     6 (74m ago)    34h
kubesphere-system              ks-controller-manager-6888fccb9c-xjvcl             1/1     Running     9 (70m ago)    34h
kubesphere-system              ks-installer-58bb4d7fcf-5ltbh                      1/1     Running     8 (74m ago)    34h
kubesphere-system              minio-69c74896fd-pl5s5                             1/1     Running     6 (74m ago)    34h
kubesphere-system              openpitrix-import-job-vbvdg                        0/1     Completed   0              72m
8 天 后
3 个月 后

KONE-XAD 大佬问个问题,监控自定义java应用,如何监控指定接口的调用和响应时间,就是如何把这个监控转变为指标,
我对prometheus不太了解,怎么把在影响小的前提下去监控一个接口。没什么思路

KONE-XAD 是想做 主动去监控 指定接口的连通性,怎么去定时调用接口,然后转换为指标暴露给prometheus