Collector yana karɓar telemetry daga aikace-aikace, sannan ya yi wata hanyar fita daban zuwa backend ɗin da aka saita. Sanya proxy a kan wannan mai fitar da HTTP na fita:

exporters:
  otlp_http/proxied:
    endpoint: https://telemetry.example:4318
    proxy_url: http://proxy.example:8080

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [otlp_http/proxied]

Haɗa wannan yanki cikin tsarin da ke akwai. Yana ɗaukan an riga an bayyana mai karɓar otlp kuma yana kiyaye processors ɗin da turawar ke buƙata da sauran saitunan bututu. Bayyana mai fitar ba tare da ambatonsa a cikin bututun da ya dace ba ba ya aika bayanai ta hanyarsa.

endpoint ya kasance tushen URL na backend ɗin telemetry. Mai fitar da OTLP HTTP yana ƙara hanyar sigina, misali /v1/traces, sai dai idan endpoint na musamman na sigina ya maye gurbinsa. proxy_url yana nuna mai shiga tsakani. Don backend ɗin gwaji wanda ba shi da mahimmanci, yana buɗaɗɗe kuma yana ba da izinin hanyar proxy na jama'a, adireshi daga jerin proxy na HTTP na iya cika wannan URL; tabbatar da isa ga ainihin host da port na backend ɗin.

Dokar upstream ta yanzu tana kiran wannan ɓangaren otlp_http kuma tana bayyana otlphttp a matsayin tsohon suna. Tsofaffin rarrabawa na iya amfani da tsohon sunan ɓangaren; ka kiyaye duka bayanin mai fitar da ambaton bututu daidai da rarrabawar da aka shigar.

Wannan tsarin abokin ciniki ne na HTTP. Mai fitar da OTLP gRPC yana da wata hanyar jigila, kuma yanayin proxy na aikace-aikacen kansa ba ya shiga kwantena ko tsarin sabis na Collector kai tsaye. Hakanan, saita mai karɓa yana magana ne da zirga-zirgar shigowa, ba wannan haɗin backend ba.

Ka kiyaye tabbatarwar TLS na backend da tabbatarwar sabis da ake buƙata. 407 na proxy da kin amincewar backend suna nuna asusu da matakai daban-daban.

Labarai masu alaƙa