How does the "jaeger client" data access "APM" via "OpenTelemetry"?

Elastic Observability APM
, ,
2

Hello @tttoad .

The OpenTelemtry Collector Exporter for Elastic has been deprecated and replaced by a native support of the OpenTelemetry Protocol (OTLP) by Elastic Observability.

Please visit our documentation OpenTelemetry integration | APM Overview [7.13] | Elastic .

Can you please ensure that you use Elastic v 7.13 and evolve the configuration of your OpenTelemetry Collector to look like:

receivers:
  jaeger:
    protocols:
      grpc:
        endpoint: 0.0.0.0:14250
exporters:
  logging/detail:
    loglevel: debug
  alibabacloud_logservice/canary:
     /*******/
  otlp/elastic:
    endpoint: "localhost:8200"
    insecure: true
    headers:
      Authorization: "Bearer my_secret_token"

processors:
  memory_limiter:
    check_interval: 1s
    limit_mib: 2000
  batch:

service:
  pipelines:
    traces:
      receivers: [ jaeger ] 
      processors: [ memory_limiter, batch ]
      exporters: [ alibabacloud_logservice/canary, otlp/elastic ]

Note that I've added the recommended batch and memory_limiter processors.

1 Like