OpenTelemetry Collector: dejinta proxy-ga soo-saare OTLP HTTP
Isticmaal dejinta proxy_url ee soo-saare OTLP HTTP oo ku xidh soo-saareha pipeline-ka dhab ahaan u dira telemetry.
Collector waxa uu telemetry ka helaa codsiyada, kadib waxa uu sameeyaa xidhiidh bixitaan oo gaar ah oo u socda backend-ka loo habeeyay. Proxy-ga saar soo-saareha HTTP bixitaanka ah:
exporters:
otlp_http/proxied:
endpoint: https://telemetry.example:4318
proxy_url: http://proxy.example:8080
service:
pipelines:
traces:
receivers: [otlp]
exporters: [otlp_http/proxied]Ku dar qaybtan habaynta jirta. Waxa ay ka fikadaysaa in qaataha otlp horey loo qeexay, waxana ay ilaalisaa processors-ka loo baahan yahay iyo dejinta kale ee pipeline-ka. Qeexidda soo-saare iyada oo aan laga tixraacin pipeline-ka khuseeya ma diro xog kasta.
endpoint wali waa URL-ka aasaasiga ah ee backend-ka telemetry. Soo-saareha OTLP HTTP waxa uu ku daraa wadada signal-ka, sida /v1/traces, haddii aan endpoint u gaar ah signal-ka beddelin. proxy_url waxa uu tilmaamaa dhexdhexaadiyaha. Backend tijaabo ah oo aan xasaasi ahayn, dadweyne ah oo ogolaada wadada proxy dadweyne, cinwaan ka socda liiska proxy HTTP ayaa buuxin kara URL-kaas; xaqiiji gelitaanka host iyo port dhabta ah ee backend-ka.
Dukumeentiga upstream ee hadda waxa uu qaybtan u yaqaannaa otlp_http, otlphttp-na waxa uu ku tilmaamaa magac hore oo duugoobay. Qaybinta hore waxa ay isticmaali kartaa magaca qaybta hore; hayso qeexidda soo-saareha iyo tixraaca pipeline-ka labadaba si waafaqsan qaybinta la rakibay.
Kani waa habayn macmiil HTTP. Soo-saareha OTLP gRPC waxa uu leeyahay gaadiid kale, deegaanka proxy ee codsiga laftiisuna si otomaatig ah uma galo weelka ama geeddi-socodka adeegga Collector. Sidoo kale, habaynta qaataha waxa ay khuseysaa taraafikada soo gasha, ma aha xidhiidhkan backend-ka.
Hayso xaqiijinta TLS ee backend-ka iyo xaqiijinta adeegga loo baahan yahay. 407 proxy iyo diidmada backend-ka waxa ay tilmaamaan akoonno iyo heerar kala duwan.