Prometheus: saita maɓallin API na manufa da http_headers da proxy_url

Lokacin da tashar ma'aunan HTTPS na buƙatar maɓallin API kuma Prometheus dole ya yi amfani da proxy na gaba, saita kan a kan buƙatar scrape ɗin kanta. Don sigar Prometheus da ke goyon bayan http_headers:

scrape_configs:
  - job_name: secured_metrics
    scheme: https
    metrics_path: /metrics
    proxy_url: http://proxy.example:8080
    http_headers:
      X-API-Key:
        files:
          - /etc/prometheus/secrets/metrics-api-key
    static_configs:
      - targets: ['metrics.example:443']

Fayil ɗin yana ɗauke da maɓallin API na manufar da ake so kuma dole ya kasance ana iya karantawa a cikin muhallin gudanar da Prometheus. A cikin kwantena, samar da shi a wannan hanyar ta gefen kwantenar.

http_headers yana sanya X-API-Key a kan buƙatar zuwa metrics.example. Ta hanyar ramin HTTPS CONNECT na yau da kullum, wannan kan yana tafiya cikin TLS na makoma. Matsakanci yana samar da haɗin kai kuma dole ya bar ramin. Don tashar ma'aunan da ake iya samu ga jama'a inda aka yarda da matsakaita na jama'a, jerin proxy na HTTP yana ba da 'yan takara don proxy_url ba tare da asusu ba; ka riƙe maɓallin API a kan buƙatar makoma.

proxy_connect_header yana da wata makoma: matsakanci yana karɓar waɗannan kanun a CONNECT. Sanya maɓallin API na manufa a can ba ya isar da shi a matsayin kan buƙatar HTTPS ga uwar garken ma'auni.

Ka riƙe ainihin sunan uwar garken ma'auni da hanyar a cikin tsarin scrape. Prometheus kuma yana kare kanun da shi kansa ya saita daga maye gurbi ba tare da izini ba, don haka yi amfani da filayen kan na musamman da aka goyi baya don wannan maɓallin API.