Saita proxy na HTTP a fitowar Elasticsearch ta Logstash

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

Ƙara wannan cikin bututun da ake da shi. hosts ya kasance wurin ƙarshen HTTP na gungu, yayin da ES_PROXY na tsarin Logstash zai iya bayar da URI da aka amince da shi kamar http://proxy.example:8080.

Bayanin fitowar Elasticsearch yana buƙatar URI na proxy kuma yana karɓar igiya mara komai a fili a matsayin ba a saita ba. Tsohuwar ƙimar da ba ta da komai ta bayanin tana ba wannan misali damar rashin samun bayyanannen proxy a inda ba a buƙata.

Ka kiyaye tabbatarwar gungu, saitin index da TLS. Gungu da ake iya samu a bainar jama’a zai iya amfani da ɗan takarar HTTP daga jerin proxy na HTTP kawai a kan hanyar da ta yarda da masu shiga tsakani na jama’a kuma ba a saita takardun shaidar proxy a cikinta ba; tabbatar da isa ga ainihin host da port na gungu. Wata fitowa na iya zaɓar wani proxy ba tare da canza kowane abokin ciniki na HTTP na Java a cikin JVM ba.

Sauyin masu canjin muhalli yana faruwa yayin da Logstash ke loda bututun. Saita mai canjin a lokacin ƙaddamar da sabis ko kwano na ainihi, ba a wani tasha da ba ta da alaƙa daga baya ba.