# Filebeat error. Returns unicode character code instead of symbol

**URL:** <https://discuss.elastic.co/t/filebeat-error-returns-unicode-character-code-instead-of-symbol/64827>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 3, 2016, 9:50am UTC](https://discuss.elastic.co/t/filebeat-error-returns-unicode-character-code-instead-of-symbol/64827 "2016-11-03T09:50:42Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![elasticheart](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elasticheart/32/65189_2.png) [@elasticheart](https://discuss.elastic.co/u/elasticheart)\
**Post date:** [November 4, 2016, 4:31am UTC](https://discuss.elastic.co/t/filebeat-error-returns-unicode-character-code-instead-of-symbol/64827/3 "2016-11-04T04:31:01Z")

</div>

Its not a problem with Filebeat, its a problem with Logstash. Logstash 2.3.4 is handling this perfectly, but issue with Logstash 5. It is showing \_grokparsefailure. It is not taking `\u003c` and `\u003e`equal to `<` and `>`

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-error-returns-unicode-character-code-instead-of-symbol/64827)._