# Filebeats to logstash \_grokparsefailure, direct to ES is fine **URL:** \ **Category:** Beats\ **Created:** [March 7, 2016, 8:33pm UTC](https://discuss.elastic.co/t/filebeats-to-logstash--grokparsefailure-direct-to-es-is-fine/43703 "2016-03-07T20:33:58Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![jwh](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jwh](https://discuss.elastic.co/u/jwh)\ **Post date:** [March 7, 2016, 8:33pm UTC](https://discuss.elastic.co/t/filebeats-to-logstash--grokparsefailure-direct-to-es-is-fine/43703/1 "2016-03-07T20:33:58Z")
I'm having issues sending syslog to logstash using filebeat, when logstash received the entry it produces a \_grokparsefailure. However if I send directly to ES everything works fine. My logstash config is [http://pastebin.com/si3vPDcE](http://pastebin.com/si3vPDcE) and it includes an example log line that was sent by my beats prospector. I've tested the message against the grok pattern at [https://grokdebug.herokuapp.com](https://grokdebug.herokuapp.com) and everything seems to be good. Any help would be appreciated. Thanks. jwh mentioning: @andrewkroh ---
**Author:** ![jwh](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jwh](https://discuss.elastic.co/u/jwh)\ **Post date:** [March 7, 2016, 9:42pm UTC](https://discuss.elastic.co/t/filebeats-to-logstash--grokparsefailure-direct-to-es-is-fine/43703/2 "2016-03-07T21:42:46Z")
Ok, issue fixed. I was trying to parse the files as though they had arrived via RELP, once I removed the grok statement completely the logs started parsing without issue. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 9:54pm UTC](https://discuss.elastic.co/t/filebeats-to-logstash--grokparsefailure-direct-to-es-is-fine/43703/3 "2017-07-05T21:54:51Z")