# Grok proccessor UI bug

**URL:** <https://discuss.elastic.co/t/grok-proccessor-ui-bug/253200>\
**Category:** Kibana\
**Created:** [October 24, 2020, 12:00pm UTC](https://discuss.elastic.co/t/grok-proccessor-ui-bug/253200 "2020-10-24T12:00:00Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![borna\_talebi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/borna_talebi/32/76317_2.png) [@borna\_talebi](https://discuss.elastic.co/u/borna_talebi)\
**Post date:** [October 24, 2020, 12:00pm UTC](https://discuss.elastic.co/t/grok-proccessor-ui-bug/253200/1 "2020-10-24T12:00:00Z")

</div>

HI,  
I'm trying a very simple grok pattern and in Grok Debugger it works fine:

 ![Screenshot from 2020-10-24 15-19-30](https://us1.discourse-cdn.com/elastic/original/3X/c/4/c43fb164678aea27460d8d7ea6ab85952c593d45.png)  
But when I tried the same pattern in ingest pipeline I got this "Bad String" Error:  
 ![Screenshot from 2020-10-24 15-21-16](https://us1.discourse-cdn.com/elastic/original/3X/1/0/10e9e09b2ec787451ec469d55751e417d64f75a6.png)  
Any idea why?

I'm using ELK 7.9.2

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 24, 2020, 12:58pm UTC](https://discuss.elastic.co/t/grok-proccessor-ui-bug/253200/2 "2020-10-24T12:58:58Z")

</div>

I think you might have to write

```
\\[%{WORD:test}\\]
```

---

<div class="post-metadata">

**Author:** ![borna\_talebi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/borna_talebi/32/76317_2.png) [@borna\_talebi](https://discuss.elastic.co/u/borna_talebi)\
**Post date:** [October 26, 2020, 5:57am UTC](https://discuss.elastic.co/t/grok-proccessor-ui-bug/253200/3 "2020-10-26T05:57:13Z")

</div>

> [@dadoonet](#):
>
> `\\[%{WORD:test}\\]`

Yep, this works fine.  
So what's the reason for different behavior between `Grok Debugger` and `Grok Processors` with escape characters?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 26, 2020, 6:55am UTC](https://discuss.elastic.co/t/grok-proccessor-ui-bug/253200/4 "2020-10-26T06:55:43Z")

</div>

I believe the Grok Debugger UI does the magic for you where the http rest API can not.

---

<div class="post-metadata">

**Author:** ![borna\_talebi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/borna_talebi/32/76317_2.png) [@borna\_talebi](https://discuss.elastic.co/u/borna_talebi)\
**Post date:** [October 26, 2020, 7:03am UTC](https://discuss.elastic.co/t/grok-proccessor-ui-bug/253200/5 "2020-10-26T07:03:53Z")

</div>

Hmm. interesting.  
Also there's something wrong with the ingest pipeline UI.  
Here I config my processor and there is no error:

 ![Screenshot from 2020-10-26 10-01-51](https://us1.discourse-cdn.com/elastic/original/3X/9/2/92b61f1bf03283baf01e880dba0aa78d960daf53.png)

I test it with `test pipeline` option and it works. but when I want to edit my processor it looks like this:

 ![Screenshot from 2020-10-26 10-02-08](https://us1.discourse-cdn.com/elastic/original/3X/3/e/3e619da76336d8ffde41d604c312fc38e7376917.png)

the pipeline still works but the config looks weird. and if I add a custom pattern (`"TESTWORD" : "\b\w+\b"`) it will change to this which is unreadable :

 ![Screenshot from 2020-10-26 10-13-07](https://us1.discourse-cdn.com/elastic/original/3X/d/0/d0e4e20404eede18fc3cf63dcd6169666535d9b9.png)

Is this a bug or this is normal?  
P.S: In preview window in `Ingest Node Pipelines` page it's showing correctly:

 ![Screenshot from 2020-10-26 10-40-15](https://us1.discourse-cdn.com/elastic/original/3X/c/c/cc25b106937a039341470bb5d965c232852126bc.png)

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 26, 2020, 8:04am UTC](https://discuss.elastic.co/t/grok-proccessor-ui-bug/253200/6 "2020-10-26T08:04:07Z")

</div>

I don't know but I moved the discussion to #elastic-stack:kibana where folks might tell if it should be reported as an issue in GitHub.

---

<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:** [November 23, 2020, 8:04am UTC](https://discuss.elastic.co/t/grok-proccessor-ui-bug/253200/7 "2020-11-23T08:04:08Z")

</div>

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