Prometheus适配器-无法从外部指标获取数据

如何解决Prometheus适配器-无法从外部指标获取数据

我无法通过运行以下命令来获取项目:kubectl get --raw "/apis/external.metrics.k8s.io/v1beta1/namespaces/default/rabbitmq_queue_messages_ready" | jq

您将在下面的输出项中看到一个空数组:

{
  "kind": "ExternalMetricValueList","apiVersion": "external.metrics.k8s.io/v1beta1","metadata": {
    "selfLink": "/apis/external.metrics.k8s.io/v1beta1/namespaces/default/rabbitmq_queue_messages_ready"
  },"items": []
}

但是,我在Prometheus端点中获得了正确的数据: 普罗米修斯网址:http:// :9090 / api / v1 / series?match%5B%5D =%7B__name __%3D〜%22%5Erabbitmq_queue _。%2A%22%7D&start = 1597255421.51 响应:

{
"status":"success","data":[
    {
        "__name__":"rabbitmq_queue_messages_ready","app":"prometheus-rabbitmq-exporter","durable":"true","instance":"10.2.0.73:9419","job":"kubernetes-pods","namespace":"default","pod_name":"rabbitmq-exporter-prometheus-rabbitmq-exporter-754c845847-gzlrq","pod_template_hash":"754c845847","queue":"test","release":"rabbitmq-exporter","vhost":"/"
    },{
        "__name__":"rabbitmq_queue_messages_ready","queue":"test1","vhost":"/"
    }
]
}

我使用以下头盔值安装了stable/prometheus-adapter

rules:
  default: false
  external:
    - seriesQuery: '{__name__=~"^rabbitmq_queue_.*"}'
      resources:
        #template: <<.Resource>>
        overrides:
          namespace:
            resource: namespace
          service:
            resource: service
          pod:
            resource: pod
      name:
        matches: ""
        as: "rabbitmq_queue_messages_ready"
      metricsQuery: 'rate(<<.Series>>{<<.LabelMatchers>>}[1m])'

Helm和Kubernetes的版本

客户端:&version.Version {SemVer:“ v2.16.9”,GitCommit:“ 8ad7037828e5a0fca1009dabe290130da6368e39”,​​GitTreeState:“ clean”} 服务器:&version.Version {SemVer:“ v2.16.7”,GitCommit:“ 5f2584fd3d35552c4af26036f0c464191287986b”,GitTreeState:“ clean”}

客户端版本:version.Info {主要:“ 1”,次要:“ 16”,GitVersion:“ v1.16.1”,GitCommit:“ d647ddbd755faf07169599a625faf302ffc34458”,GitTreeState:“干净”,构建日期:“ 2019-10-02T17 :01:15Z“,GoVersion:” go1.12.10“,编译器:” gc“,平台:” darwin / amd64“} 服务器版本:version.Info {主要:“ 1”,次要:“ 15”,GitVersion:“ v1.15.11”,GitCommit:“ ec831747a3a5896dbdf53f259eafea2a2595217c”,GitTreeState:“干净”,构建日期:“ 2020-05-29T19:56: 10Z”,GoVersion:“ go1.12.17”,编译器:“ gc”,平台:“ linux / amd64”}

预期结果: 它应该从Prometheus获取指标

如何复制: 使用上述配置安装stable/prometheus-rabbitmq-exporterstable/prometheus-adapter舵图。

我正在遵循本指南:https://nuvalence.io/building-a-k8s-autoscaler-with-custom-metrics/

解决方法

首先要进一步解决您的问题,我会在舞会适配器设置中检查几件事:

  1. 使用"kubectl get --raw ..."命令直接获取指标时,您在Prometheus适配器日志中是否看到任何错误?
  2. 您已将prometheus-adapter安装到哪个命名空间? (询问,因为当我将其部署到“ kube-system”以外的另一个ns时,我曾经在适配器日志中观察到RBAC相关的错误)
  3. 能否请您粘贴最终的“ prom-adapter” /etc/adapter/config.yaml配置的内容(来自prom-adapter的Pod)

我正在使用适配器公开相同的外部Rabbitmq指标,没有任何问题,请检查同一命令的输出:

{
  "kind": "ExternalMetricValueList","apiVersion": "external.metrics.k8s.io/v1beta1","metadata": {
    "selfLink": "/apis/external.metrics.k8s.io/v1beta1/namespaces/default/rabbitmq_queue_messages_ready"
  },"items": [
    {
      "metricName": "rabbitmq_queue_messages_ready","metricLabels": {
        "endpoint": "metrics","instance": "10.64.1.97:9419","job": "rabbitmq","namespace": "default","pod": "rabbitmq-0","service": "rabbitmq"
      },"timestamp": "2020-08-13T23:50:29Z","value": "174160m"
    }
  ]
}

使用的舞会适配器版本directxman12/k8s-prometheus-adapter-amd64:v0.6.0

///使用社区Wiki帖子以提高清晰度(代码段格式等)

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-