# Logstash GROK Visualize

**URL:** <https://discuss.elastic.co/t/logstash-grok-visualize/59939>\
**Category:** Logstash\
**Created:** [September 7, 2016, 4:35am UTC](https://discuss.elastic.co/t/logstash-grok-visualize/59939 "2016-09-07T04:35:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![somerandomguy](https://avatars.discourse-cdn.com/v4/letter/s/e19b73/32.png) [@somerandomguy](https://discuss.elastic.co/u/somerandomguy)\
**Post date:** [September 7, 2016, 4:35am UTC](https://discuss.elastic.co/t/logstash-grok-visualize/59939/1 "2016-09-07T04:35:35Z")

</div>

Hi, I am using GROK to split out my log messages into fields.  
Some message fields have multiple words as a result e.g. login authentication succeeded or login authentication failed.  
When I go to Kibana, Discover, find the log and then on the left hand side pane expand the relivant field I can see them both one above the other l but when I click on visualise it creates 4 bar charts "authentication", "login", "succeeded" and "failed".

Have noticed I also have a warning message next to Visualize - 1 warning - This is an analyzed string field. Analyzed strings are highly unique and can use a lot of memory to visualize.....

Is there any way to fix up the GROK to keep the messages together.

In GROK I'm capturing this part as %{CISCO\_REASON:login\_authentication\_response}.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [September 7, 2016, 6:14am UTC](https://discuss.elastic.co/t/logstash-grok-visualize/59939/2 "2016-09-07T06:14:17Z")

</div>

This is unrelated to grok. The problem is that the field stored in Elasticsearch is analyzed. You should have a .raw subfield that you can use, or you can use an index template to change the field's configuration to not be analyzed.

---

<div class="post-metadata">

**Author:** ![somerandomguy](https://avatars.discourse-cdn.com/v4/letter/s/e19b73/32.png) [@somerandomguy](https://discuss.elastic.co/u/somerandomguy)\
**Post date:** [September 7, 2016, 6:26am UTC](https://discuss.elastic.co/t/logstash-grok-visualize/59939/3 "2016-09-07T06:26:10Z")

</div>

Thanks Magnus.  
Got any good links with examples on how I can do this?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [September 7, 2016, 7:37am UTC](https://discuss.elastic.co/t/logstash-grok-visualize/59939/4 "2016-09-07T07:37:30Z")

</div>

I don't have anything specific but index templates and how to mark fields as non-analyzed has been covered here many many times before and index templates in general is of course included in the ES documentation.

---

<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:** [July 6, 2017, 4:39am UTC](https://discuss.elastic.co/t/logstash-grok-visualize/59939/5 "2017-07-06T04:39:35Z")

</div>

Closed on July 6, 2017, 4:39am UTC