# Provided Grok expressions do not match field value for response code 408

**URL:** <https://discuss.elastic.co/t/provided-grok-expressions-do-not-match-field-value-for-response-code-408/133776>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [May 30, 2018, 2:56am UTC](https://discuss.elastic.co/t/provided-grok-expressions-do-not-match-field-value-for-response-code-408/133776 "2018-05-30T02:56:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gregbacchus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gregbacchus/32/31720_2.png) [@gregbacchus](https://discuss.elastic.co/u/gregbacchus)\
**Post date:** [May 30, 2018, 2:56am UTC](https://discuss.elastic.co/t/provided-grok-expressions-do-not-match-field-value-for-response-code-408/133776/1 "2018-05-30T02:56:53Z")

</div>

Hi,

I'm using Filebeat 6.2.4 with the apache module (and Apache 2.4.7).  
My other\_vhosts\_access.log contains some logs like below:

```
my-host-name.com:80 1.2.3.4 - - [30/May/2018:02:14:12 +0000] "-" 408 0 "-" "-"

```

and when sent into Elasticsearch, it shows with with an error:

```
Provided Grok expressions do not match field value: [my-host-name.com:80 1.2.3.4 - - [30/May/2018:02:14:12 +0000] \"-\" 408 0 \"-\" \"-\"]

```

I have identified that this can easily be fixed with a minor tweak to the ingest pipeline by changing

```
"%{IPORHOST:apache2.access.remote_ip} - %{DATA:apache2.access.user_name} \\[%{HTTPDATE:apache2.access.time}\\] \"-\" %{NUMBER:apache2.access.response_code} -"

```

to

```
"%{IPORHOST:apache2.access.remote_ip} - %{DATA:apache2.access.user_name} \\[%{HTTPDATE:apache2.access.time}\\] \"-\" %{NUMBER:apache2.access.response_code} "

```

(note removal of trailing `hyphen`).

---

<div class="post-metadata">

**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\
**Post date:** [June 1, 2018, 9:18am UTC](https://discuss.elastic.co/t/provided-grok-expressions-do-not-match-field-value-for-response-code-408/133776/2 "2018-06-01T09:18:29Z")

</div>

Do you mind opening a PR for this? Also, what OS are you running Apache on?

---

<div class="post-metadata">

**Author:** ![gregbacchus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gregbacchus/32/31720_2.png) [@gregbacchus](https://discuss.elastic.co/u/gregbacchus)\
**Post date:** [June 6, 2018, 2:04am UTC](https://discuss.elastic.co/t/provided-grok-expressions-do-not-match-field-value-for-response-code-408/133776/3 "2018-06-06T02:04:39Z")

</div>

Sure. I'll create one shortly. It's running on Ubuntu 14.04.

---

<div class="post-metadata">

**Author:** ![gregbacchus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gregbacchus/32/31720_2.png) [@gregbacchus](https://discuss.elastic.co/u/gregbacchus)\
**Post date:** [June 7, 2018, 10:16pm UTC](https://discuss.elastic.co/t/provided-grok-expressions-do-not-match-field-value-for-response-code-408/133776/4 "2018-06-07T22:16:00Z")

</div>

> <https://github.com/elastic/beats/pull/7280>

---

<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 5, 2018, 10:18pm UTC](https://discuss.elastic.co/t/provided-grok-expressions-do-not-match-field-value-for-response-code-408/133776/5 "2018-07-05T22:18:10Z")

</div>

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