# Issue with otlp-collectors and elastic

**URL:** <https://discuss.elastic.co/t/issue-with-otlp-collectors-and-elastic/361584>\
**Category:** Elasticsearch\
**Created:** [June 17, 2024, 2:28pm UTC](https://discuss.elastic.co/t/issue-with-otlp-collectors-and-elastic/361584 "2024-06-17T14:28:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![iamp3](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iamp3/32/125051_2.png) [@iamp3](https://discuss.elastic.co/u/iamp3)\
**Post date:** [June 17, 2024, 2:28pm UTC](https://discuss.elastic.co/t/issue-with-otlp-collectors-and-elastic/361584/1 "2024-06-17T14:28:50Z")

</div>

Hi, It looks like smth block search/view of metric data in real-time mode (from otel-collectors) and produces this data incrementally. For example, on 12 June I could check data till 01:00, but at 13 June I could see data till 07:00 12 June.

On dashboards side:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/3/43960332e651706a72bf207d5edac9ec8f33da5a.png)

I see this on otlp-collectors log:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/b/bb56c303205993cd0b15cb136cc1b4b98c394e38.jpeg)

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [June 20, 2024, 5:16pm UTC](https://discuss.elastic.co/t/issue-with-otlp-collectors-and-elastic/361584/2 "2024-06-20T17:16:19Z")

</div>

Thanks for reaching out, @iamp3. Please provide some further context as to the issue you are facing and what you expect to see versus what you are seeing. Also, since screenshots can be hard to read, could you paste in the errors you are receiving?

---

<div class="post-metadata">

**Author:** ![iamp3](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iamp3/32/125051_2.png) [@iamp3](https://discuss.elastic.co/u/iamp3)\
**Post date:** [August 23, 2024, 9:29am UTC](https://discuss.elastic.co/t/issue-with-otlp-collectors-and-elastic/361584/3 "2024-08-23T09:29:30Z")

</div>

Sorry for late response, logs:

```auto
Value: 0
    {"kind": "exporter", "data_type": "metrics", "name": "logging"}
2024-08-23T09:21:28.238Z info exporterhelper/retry_sender.go:129 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "otlp/elastic", "error": "rpc error: code = DeadlineExceeded desc = context deadline exceeded", "interval": "53.841742873s"}
2024-08-23T09:21:30.219Z info exporterhelper/retry_sender.go:129 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "otlp/elastic", "error": "rpc error: code = DeadlineExceeded desc = context deadline exceeded", "interval": "1m9.974494263s"}
2024-08-23T09:21:45.116Z info exporterhelper/retry_sender.go:129 Exporting failed. Will retry the request after interval. {"kind": "exporter", "data_type": "metrics", "name": "otlp/elastic", "error": "rpc error: code = DeadlineExceeded desc = context deadline exceeded", "interval": "43.117012577s"}
2024-08-23T09:21:46.499Z error exporterhelper/queue_sender.go:125 Exporting failed. No more retries left. Dropping data. {"kind": "exporter", "data_type": "metrics", "name": "otlp/elastic", "error": "max elapsed time expired rpc error: code = DeadlineExceeded desc = context deadline exceeded", "dropped_items": 209}

```

We expect to see metrics/traces on elk side, but looks liike most of our data dropped with the error above

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [August 26, 2024, 5:24pm UTC](https://discuss.elastic.co/t/issue-with-otlp-collectors-and-elastic/361584/4 "2024-08-26T17:24:06Z")

</div>

Thanks for following up, @iamp3.

Here are a few ideas to consider:

- You will want to ensure that you have configured both exporters (gRPC and HTTP) to use different ports  
Double-check that you are correctly configuring the OTLP exporter and that your network is configured correctly to connect to the Elastic OTLP endpoint.
- Here is an example of a collector I recently used, which could be helpful:

> <https://github.com/JessicaGarson/Introduction-to-OpenTelemetry-with-Flask/blob/main/tmp/otel-collector-config.yaml>

Do you have the YAML configuration file you can send over? You may also want to check out our [documentation on the subject](https://www.elastic.co/guide/en/observability/current/apm-open-telemetry-direct.html).