# \[solved\] Problems with "/" as value / apache logs in logstash

**URL:** <https://discuss.elastic.co/t/solved-problems-with-as-value-apache-logs-in-logstash/129931>\
**Category:** Elasticsearch\
**Created:** [April 28, 2018, 7:57pm UTC](https://discuss.elastic.co/t/solved-problems-with-as-value-apache-logs-in-logstash/129931 "2018-04-28T19:57:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sushimaster](https://avatars.discourse-cdn.com/v4/letter/s/919ad9/32.png) [@Sushimaster](https://discuss.elastic.co/u/Sushimaster)\
**Post date:** [April 28, 2018, 7:57pm UTC](https://discuss.elastic.co/t/solved-problems-with-as-value-apache-logs-in-logstash/129931/1 "2018-04-28T19:57:37Z")

</div>

Hi,

I'm pipelining Apache logfiles from logstash to elasticsearch, implemented very close to the example in the logstash docs.

Now when the "request" field just has an / (slash) as value, it appears in the Discover tab

 ![elastic1](https://us1.discourse-cdn.com/elastic/original/3X/9/a/9aed5be79a114f5754d18a40d70c606a6b0df650.png)

However, when I try to filter out just the / requests, it fails.

 ![elastic2](https://us1.discourse-cdn.com/elastic/original/3X/e/1/e1f9b56b521c061b2395e957a4cce10d365bcc03.png)

When using the "request" field as grouping term, all the / entries are missing.

Is this kinda bug, or do I have to change something?

EDIT: Switched to Elasticsearch forum, hope someone can help

---

<div class="post-metadata">

**Author:** ![Sushimaster](https://avatars.discourse-cdn.com/v4/letter/s/919ad9/32.png) [@Sushimaster](https://discuss.elastic.co/u/Sushimaster)\
**Post date:** [May 3, 2018, 9:28am UTC](https://discuss.elastic.co/t/solved-problems-with-as-value-apache-logs-in-logstash/129931/2 "2018-05-03T09:28:29Z")

</div>

Can at least someone verify this issue?

---

<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:** [May 3, 2018, 9:57am UTC](https://discuss.elastic.co/t/solved-problems-with-as-value-apache-logs-in-logstash/129931/3 "2018-05-03T09:57:05Z")

</div>

I'd say that probably with the default analyzer `/` is not indexed at all.  
May be change the default analyzer for this field to something like a path tokenizer or search in request.keyword instead ?

---

<div class="post-metadata">

**Author:** ![Sushimaster](https://avatars.discourse-cdn.com/v4/letter/s/919ad9/32.png) [@Sushimaster](https://discuss.elastic.co/u/Sushimaster)\
**Post date:** [May 3, 2018, 10:57am UTC](https://discuss.elastic.co/t/solved-problems-with-as-value-apache-logs-in-logstash/129931/4 "2018-05-03T10:57:39Z")

</div>

Yes, you're right, when I use "request.keyword" as search term instead of "request", it works. Weird.  
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:** [May 31, 2018, 10:57am UTC](https://discuss.elastic.co/t/solved-problems-with-as-value-apache-logs-in-logstash/129931/5 "2018-05-31T10:57:42Z")

</div>

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