# serverMap Module data exceptions

**URL:** <https://discuss.elastic.co/t/servermap-module-data-exceptions/278012>\
**Category:** APM\
**Tags:** docker, go, server\
**Created:** [July 7, 2021, 3:51am UTC](https://discuss.elastic.co/t/servermap-module-data-exceptions/278012 "2021-07-07T03:51:09Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![cyrilleleclerc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cyrilleleclerc/32/60493_2.png) [@cyrilleleclerc](https://discuss.elastic.co/u/cyrilleleclerc)\
**Post date:** [July 12, 2021, 2:01pm UTC](https://discuss.elastic.co/t/servermap-module-data-exceptions/278012/5 "2021-07-12T14:01:39Z")

</div>

Hello @tttoad ,

As discussed on [How does the "jaeger client" data access "APM" via "OpenTelemetry"?](https://discuss.elastic.co/t/how-does-the-jaeger-client-data-access-apm-via-opentelemetry/278375) , 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](https://www.elastic.co/guide/en/apm/get-started/current/open-telemetry-elastic.html) .

The collector configuration will look like:

```auto
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]

```

---

_[View the full topic](https://discuss.elastic.co/t/servermap-module-data-exceptions/278012)._