# Logstash crashed down the elasticsearch

**URL:** <https://discuss.elastic.co/t/logstash-crashed-down-the-elasticsearch/194935>\
**Category:** Logstash\
**Created:** [August 13, 2019, 12:27am UTC](https://discuss.elastic.co/t/logstash-crashed-down-the-elasticsearch/194935 "2019-08-13T00:27:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tianji\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tianji_zhao/32/48260_2.png) [@Tianji\_Zhao](https://discuss.elastic.co/u/Tianji_Zhao)\
**Post date:** [August 13, 2019, 12:27am UTC](https://discuss.elastic.co/t/logstash-crashed-down-the-elasticsearch/194935/1 "2019-08-13T00:27:27Z")

</div>

I use a logstash to fetching the data from the elasticsearch.  
The logstash works well when I use an empty filter. But it crashes the remote elastic when I add a json filter.  
The logstash.cong is as follow:

input{  
elasticsearch{  
hosts =\> "10.117.6.7"  
}  
}

filter{  
json{  
source =\> "message"  
}  
}

output{  
stdout{codec =\> rubydebug}  
}

---

<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:** [August 13, 2019, 12:37am UTC](https://discuss.elastic.co/t/logstash-crashed-down-the-elasticsearch/194935/2 "2019-08-13T00:37:10Z")

</div>

It would be very unusual for you to need a json filter to parse the [message] field from an elasticsearch input. It is possible, but unusual.

What do you mean by "it crashes the remote elastic".

---

<div class="post-metadata">

**Author:** ![Tianji\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tianji_zhao/32/48260_2.png) [@Tianji\_Zhao](https://discuss.elastic.co/u/Tianji_Zhao)\
**Post date:** [August 13, 2019, 12:43am UTC](https://discuss.elastic.co/t/logstash-crashed-down-the-elasticsearch/194935/3 "2019-08-13T00:43:40Z")

</div>

I mean when I create a logstash above, the elastic I am fetching from(in this case the elastic in 10.117.6.7) crashed down (closed ).

If I want to read the "message" field from the elastic and filter on it, which filter I would use?

---

<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:** [August 13, 2019, 2:55pm UTC](https://discuss.elastic.co/t/logstash-crashed-down-the-elasticsearch/194935/4 "2019-08-13T14:55:46Z")

</div>

OK, if elasticsearch crashes I would expect it to log a message explaining why. You should open a thread in the elasticsearch forum including the message and asking for help with it.

If the [message] field contains JSON then a json filter is OK.

---

<div class="post-metadata">

**Author:** ![Tianji\_Zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tianji_zhao/32/48260_2.png) [@Tianji\_Zhao](https://discuss.elastic.co/u/Tianji_Zhao)\
**Post date:** [August 14, 2019, 12:40am UTC](https://discuss.elastic.co/t/logstash-crashed-down-the-elasticsearch/194935/5 "2019-08-14T00:40:02Z")

</div>

Thanks, the problem has been solved. I delete some white space in the filter and use grok instead.

---

<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:** [September 11, 2019, 12:40am UTC](https://discuss.elastic.co/t/logstash-crashed-down-the-elasticsearch/194935/6 "2019-09-11T00:40:07Z")

</div>

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