Setha i-HTTP proxy kumphumela we-Elasticsearch we-Logstash

Hlela i-proxy URI ye-Elasticsearch output plugin ngqo esikhundleni sokuncika kuzici zokuxhumana ze-JVM yonke.

output {
  elasticsearch {
    id => "remote_cluster"
    hosts => ["https://es.example:9200"]
    proxy => "${ES_PROXY:}"
  }
}

Engeza lokhu ku-pipeline ekhona. I-hosts ihlala iyindawo yokugcina ye-HTTP yeqembu, kuyilapho i-ES_PROXY yenqubo ye-Logstash inganikeza i-URI egunyaziwe njenge-http://proxy.example:8080.

Isithenjwa somphumela we-Elasticsearch sidinga i-proxy URI futhi samukela ngokusobala umucu ongenalutho njengongasethiwe. Inani elizenzakalelayo elingenalutho lesisho livumela le nsiza ukuthi ingabi nayo i-proxy ecacile lapho ingadingeki khona.

Gcina ukuqinisekiswa kweqembu, izilungiselelo ze-index ne-TLS. Iqembu elifinyeleleka emphakathini lingasebenzisa kuphela umfakisicelo we-HTTP ovela kuhlu lwe-HTTP proxy emzileni ovumela abalamuli bomphakathi nongenalwazi lokuqinisekisa lwe-proxy oluhleliwe; qinisekisa ukufinyelela ku-host ne-port yangempela yeqembu. Omunye umphumela ungakhetha enye i-proxy ngaphandle kokushintsha iklayenti ngalinye le-Java HTTP ku-JVM.

Ukufakwa esikhundleni kweziguquguquki zemvelo kwenzeka ngesikhathi i-Logstash ilayisha i-pipeline. Setha isiguquguquki ngesikhathi sokuqaliswa kwensizakalo noma kwekonthena yangempela, hhayi kwelinye ithiminali elingahlobene kamuva.

Izihloko ezihlobene