使用普罗米修斯为HTTP和HTTPS端口刮取kubernetes容器的度量标准

时间:2018-05-04 16:05:34

标签: kubernetes prometheus

我们希望我们的Prometheus安装能够在pod中抓取两个容器的指标。 一个容器通过HTTPS在端口443公开指标,而另一个容器通过HTTP在端口8080公开它们。两个容器都在同一路径上提供指标,即/metrics

如果我们将 prometheus.io/scheme 声明为http或https,则只会抓取一个容器。对于我们总是收到的另一个:server returned HTTP status 400 Bad Request 如果我们根本没有定义 prometheus.io/scheme ,也会发生同样的情况。然后,普罗米修斯将对两个端口使用http,并且对于在端口443公开指标的容器失败,因为它只是预期的HTTPS请求。

有没有办法告诉普罗米修斯如何在我们的部署中刮掉各个容器?获取两个容器的指标有哪些可行的解决方法?

版本

Kubernetes:1.10.2

普罗米修斯:2.2.1

部署摘录

apiVersion: apps/v1
kind: Deployment
metadata:
  name: xxx
  namespace: xxx
spec:
  selector:
    matchLabels:
      app: xxx
  template:
    metadata:
      labels:
        app: xxx
      annotations:
        prometheus.io/scrape: "true"
        prometheus.io/path: "/metrics"
    spec:
      containers:
      - name: container-1
        image: xxx
        ports:
        - containerPort: 443
      - name: container-2
        image: xxx
        ports:
        - containerPort: 8080

普罗米修斯配置:

- job_name: kubernetes-pods
  scrape_interval: 1m
  scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  kubernetes_sd_configs:
  - api_server: null
    role: pod
    namespaces:
      names: []
  relabel_configs:
  - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]
    separator: ;
    regex: "true"
    replacement: $1
    action: keep
  - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]
    separator: ;
    regex: (.+)
    target_label: __metrics_path__
    replacement: $1
    action: replace
  - source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]
    separator: ;
    regex: ([^:]+)(?::\d+)?;(\d+)
    target_label: __address__
    replacement: $1:$2
    action: replace
  - separator: ;
    regex: __meta_kubernetes_pod_label_(.+)
    replacement: $1
    action: labelmap
  - source_labels: [__meta_kubernetes_namespace]
    separator: ;
    regex: (.*)
    target_label: kubernetes_namespace
    replacement: $1
    action: replace
  - source_labels: [__meta_kubernetes_pod_name]
    separator: ;
    regex: (.*)
    target_label: kubernetes_pod_name
    replacement: $1
    action: replace

2 个答案:

答案 0 :(得分:2)

我找到了一个GIST代码段,如果它被命名为" metrics",则直接从容器中获取端口,而不是依赖于每个pod注释。它还包含一个注释,使其成为以" metrics"开头的任何端口的正则表达式。

也许您可以扩展它以从端口名称中提取架构,例如" metrics-http"和" metrics-https"。

https://gist.github.com/bakins/5bf7d4e719f36c1c555d81134d8887eb

# 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. This
#    will be the same for every container in the pod that is scraped.
# * this will scrape every container in a pod with `prometheus.io/scrape` set to true and the
    port is name `metrics` in the container
# * note `prometheus.io/port` is no longer honored. You must name the port(s) to scrape `metrics`
#   Also, in some of the issues I read, there was mention of a container role, but I couldn't get 
#   that to work - or find any more info on it.
- 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_container_port_name]
    action: keep
    regex: metrics
  - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]
    action: replace
    target_label: __metrics_path__
    regex: (.+)
  - source_labels: [ __address__, __meta_kubernetes_pod_container_port_number]
    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

答案 1 :(得分:0)

您不仅限于在部署清单中添加prometheus注释。事实上,我将它们添加到kubernetes服务清单上。

这意味着您可以为container-1添加一个服务,为container-2添加另一个服务。 Bith将被prometheus刮掉