# Logstash \[7.8\] problem with an elastic update doc

**URL:** <https://discuss.elastic.co/t/logstash-7-8-problem-with-an-elastic-update-doc/253370>\
**Category:** Logstash\
**Created:** [October 26, 2020, 11:41pm UTC](https://discuss.elastic.co/t/logstash-7-8-problem-with-an-elastic-update-doc/253370 "2020-10-26T23:41:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![unknown\_user](https://avatars.discourse-cdn.com/v4/letter/u/ac91a4/32.png) [@unknown\_user](https://discuss.elastic.co/u/unknown_user)\
**Post date:** [October 26, 2020, 11:41pm UTC](https://discuss.elastic.co/t/logstash-7-8-problem-with-an-elastic-update-doc/253370/1 "2020-10-26T23:41:46Z")

</div>

Hi Guys,

Running into a bit of an issue that I am trying to overcome.

I have a index that only updates documents, specifically I am monitoring devices that are either in an UP or DOWN status and the doc\_id is the name of the device. The issue i have is that when there is a DOWN / UP in really quick succession it can't workout which is the latest status as it seems to bulk post to elasticsearch

Initially, i thought that the 4 pipeline workers was causing the problem and transferred the doc's i need to update to a new pipeline with a single worker. This still didn't fix the issue so i set the pipeline.batch.delay,

```auto
pipeline.batch.delay: 2

```

Still having the issue with the batch post not knowing what the latest status is.

Can anyone provide any work around for this? I was thinking of maybe trying the aggregate plugin to solve this issue.

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [October 27, 2020, 2:36pm UTC](https://discuss.elastic.co/t/logstash-7-8-problem-with-an-elastic-update-doc/253370/2 "2020-10-27T14:36:53Z")

</div>

If you want to avoid the batching that the elasticsearch output does you could use an http filter to send the data to elasticsearch.

---

<div class="post-metadata">

**Author:** ![unknown\_user](https://avatars.discourse-cdn.com/v4/letter/u/ac91a4/32.png) [@unknown\_user](https://discuss.elastic.co/u/unknown_user)\
**Post date:** [October 27, 2020, 10:27pm UTC](https://discuss.elastic.co/t/logstash-7-8-problem-with-an-elastic-update-doc/253370/3 "2020-10-27T22:27:34Z")

</div>

Thanks @Badger I haven't used the http filter to send to elasticsearch before.

I'll investigate and see how it goes.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 24, 2020, 10:27pm UTC](https://discuss.elastic.co/t/logstash-7-8-problem-with-an-elastic-update-doc/253370/4 "2020-11-24T22:27:51Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.