Hello @tttoad ,
As discussed on How does the "jaeger client" data access "APM" via "OpenTelemetry"? , I recommend you to use the Elastic OpenTelemetry Protocol native support rather than the OpenTelemetry Collector Exporter for Elastic that has been deprecated few months ago.
See our documentation OpenTelemetry integration | APM Overview [7.13] | Elastic .
The collector configuration will 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 ]