# Grok match handel special characters, \_grokparsefailure

**URL:** https://discuss.elastic.co/t/grok-match-handel-special-characters--grokparsefailure/55417
**Category:** Logstash
**Created:** [July 13, 2016, 2:10pm UTC](https://discuss.elastic.co/t/grok-match-handel-special-characters--grokparsefailure/55417 "2016-07-13T14:10:30Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![govereem](https://avatars.discourse-cdn.com/v4/letter/g/b9e5f3/32.png) [@govereem](https://discuss.elastic.co/u/govereem)
#### Post date: [July 13, 2016, 2:10pm UTC](https://discuss.elastic.co/t/grok-match-handel-special-characters--grokparsefailure/55417/1 "2016-07-13T14:10:30Z")

</div>

I'm using this grok code  
grok {  
# check that fields match your IIS log settings  
match =\> ["message", "%{TIMESTAMP\_ISO8601:log\_timestamp} %{IPORHOST:site} %{WORD:method} %{URIPATH:page} %{NOTSPACE:querystring} %{NUMBER:port} %{NOTSPACE:username} %{IPORHOST:clienthost} %{NOTSPACE:useragent} %{NUMBER:response} %{NUMBER:subresponse} %{NUMBER:scstatus} %{NUMBER:time\_taken}"]  
}

This fails "\_grokparsefailure" when the page / url has [1].jpg in them or characters with ë or ä in the url etc.

Wat solution is there?

---

<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: [July 13, 2016, 2:25pm UTC](https://discuss.elastic.co/t/grok-match-handel-special-characters--grokparsefailure/55417/2 "2016-07-13T14:25:09Z")

</div>

The URIPATH pattern is probably too restrictive. Use NOTSPACE instead of URIPATH for capturing the `page` field?

---

<div class="post-metadata">

### Author: ![govereem](https://avatars.discourse-cdn.com/v4/letter/g/b9e5f3/32.png) [@govereem](https://discuss.elastic.co/u/govereem)
#### Post date: [July 14, 2016, 7:01am UTC](https://discuss.elastic.co/t/grok-match-handel-special-characters--grokparsefailure/55417/3 "2016-07-14T07:01:08Z")

</div>

Thank you for the quick answer, I will try it out, I just saw this section, what I couldn’t find yesterday [\_grokparsefailure when parsing IIS logs if the %{URIPATH:page} has square brackets [] in it](https://discuss.elastic.co/t/-grokparsefailure-when-parsing-iis-logs-if-the-uripath-page-has-square-brackets-in-it/33416) were you answered the same.

---

<div class="post-metadata">

### Author: ![rasmusraadberg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rasmusraadberg/32/18687_2.png) [@rasmusraadberg](https://discuss.elastic.co/u/rasmusraadberg)
#### Post date: [May 31, 2017, 12:14pm UTC](https://discuss.elastic.co/t/grok-match-handel-special-characters--grokparsefailure/55417/4 "2017-05-31T12:14:11Z")

</div>

Exactly the answer I was looking for debugging danish characters in page.  
Thank you

---

<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:26am UTC](https://discuss.elastic.co/t/grok-match-handel-special-characters--grokparsefailure/55417/5 "2017-07-06T04:26:12Z")

</div>


