# Parsing Redis log message field using Redis module but shipping to Logstash **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [May 10, 2019, 1:10pm UTC](https://discuss.elastic.co/t/parsing-redis-log-message-field-using-redis-module-but-shipping-to-logstash/180563 "2019-05-10T13:10:20Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![A\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/a_b/32/17104_2.png) [@A\_B](https://discuss.elastic.co/u/A_B)\ **Post date:** [May 10, 2019, 1:10pm UTC](https://discuss.elastic.co/t/parsing-redis-log-message-field-using-redis-module-but-shipping-to-logstash/180563/1 "2019-05-10T13:10:21Z")
Hello all, I am testing the Redis module for Filebeat. Filebeat uses Logstash as the output. The log messages are not parsed as I had expected. Based on this from the documentation > Uses ingest node to parse and process the log lines, shaping the data into a structure suitable for visualizing in Kibana I assume this is because I do not ship the logs directly to Elasticsearch. Is there a way to get the same functionality when going through Logstash? I mean "for free" 🙂 I can do it with e.g. `grok` but maybe there is something straight out of the box 😃 I am going through Logstash because the same host has other logs that go through Logstash and according to the Filebeat output [documentation](https://www.elastic.co/guide/en/beats/filebeat/7.0/configuring-output.html) > Only a single output may be defined. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 7, 2019, 1:10pm UTC](https://discuss.elastic.co/t/parsing-redis-log-message-field-using-redis-module-but-shipping-to-logstash/180563/2 "2019-06-07T13:10:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.