# Opentelemetry issue
**URL:** https://discuss.elastic.co/t/opentelemetry-issue/248394
**Category:** APM
**Tags:** server
**Created:** [September 12, 2020, 1:00am UTC](https://discuss.elastic.co/t/opentelemetry-issue/248394 "2020-09-12T01:00:01Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Renz2018](https://discuss.elastic.co/u/Renz2018)
#### Post date: [September 12, 2020, 1:00am UTC](https://discuss.elastic.co/t/opentelemetry-issue/248394/1 "2020-09-12T01:00:01Z")
Hello, guys:
**Kibana version** : 7.7.1
**Elasticsearch version** : 7.7.1
1. If I use opentelemetry agent, what's the difference between I send data directly to apm server( use apm jaeger port) and I send data to opentelemetry collector elastic exporter , export send to apm server? Which pipeline is recommend?
---
### Author:  [@axw](https://discuss.elastic.co/u/axw)
#### Post date: [September 13, 2020, 5:33am UTC](https://discuss.elastic.co/t/opentelemetry-issue/248394/2 "2020-09-13T05:33:43Z")
@Renz2018 Welcome to the forum!
My suggestions:
- If you're instrumenting your application with an OpenTelemetry SDK, use the OpenTelemetry Collector exporter
- If you're instrumenting your application with a Jaeger client, then use APM Server's Jaeger intake
Apart from the fact that the Jaeger intake is a bit more mature, as it was developed first, a couple of other reasons why you might want to use it for now:
- as it is Jaeger-specific, it takes into account details like Jaeger's sampling tags in order to calculate accurate metrics
- it supports Jaeger's remote sampling API, so you can configure the sampling rate dynamically
If you're using the OpenTelemetry SDK in your application, then the above points are irrelevant.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 4, 2020, 1:33am UTC](https://discuss.elastic.co/t/opentelemetry-issue/248394/3 "2020-10-04T01:33:55Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.