# \_geoip\_lookup\_failure but not specified

**URL:** <https://discuss.elastic.co/t/geoip-lookup-failure-but-not-specified/111348>\
**Category:** Logstash\
**Created:** [December 12, 2017, 1:51pm UTC](https://discuss.elastic.co/t/geoip-lookup-failure-but-not-specified/111348 "2017-12-12T13:51:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![teejayuu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/teejayuu/32/18356_2.png) [@teejayuu](https://discuss.elastic.co/u/teejayuu)\
**Post date:** [December 12, 2017, 1:51pm UTC](https://discuss.elastic.co/t/geoip-lookup-failure-but-not-specified/111348/1 "2017-12-12T13:51:06Z")

</div>

Using filebeat to send IIS logs from Windows System and to my logstash server and then to elastic search and Kibana.  
Elastic search and Kibana - 5.3.2 Logstash and filebeat - 5.3.2  
filebeat.yml :

```
#=========================== Filebeat prospectors
- input_type: log 
# Paths that should be crawled and fetched. Glob based paths.
  paths:
# Add the path to IIS Logs
    - d:\Inetpub\logs\logfiles\*\*
  document_type: iis
#-------------------------- Elasticsearch output -------------
# Comment out
#output.elasticsearch:
  # Array of hosts to connect to.
  #hosts: ["localhost:9200"]
#----------------------------- Logstash output ---------------
# Uncomment and set Logstash IP
output.logstash:
  # The Logstash hosts
  hosts: ["nemesis.hstv.local:5044"]
  # Optional index name. The default index name is set to name of the beat
  # in all lowercase.
  index: 'filebeat_iis'

```

iis-filter.conf:

```
 filter {
  if [type] == "iis" {
    grok {
      match => { "message" => "%{TIMESTAMP_ISO8601:log_timestamp} %{WORD:S-SiteName} %{NOTSPACE:S-ComputerName} %{IPORHOST:S-IP} %{WORD:CS-Method} %{URIPATH:CS-URI-Stem} (?:-|\"%{URIPATH:CS-URI-Query}\") %{NUMBER:S-Port} %{NOTSPACE:CS-Username} %{IPORHOST:C-IP} %{NOTSPACE:CS-Version} %{NOTSPACE:CS-UserAgent} %{NOTSPACE:CS-Cookie} %{NOTSPACE:CS-Referer} %{NOTSPACE:CS-Host} %{NUMBER:SC-Status} %{NUMBER:SC-SubStatus} %{NUMBER:SC-Win32-Status} %{NUMBER:SC-Bytes} %{NUMBER:CS-Bytes} %{NUMBER:Time-Taken}"}
    }
  }
}

```

When I view the filebeat\_iis in Kibana - Discover, every entry has 2 tags:

```
beats_input_codec_plain_applied
_geoip_lookup_failure

```

Why do I get the \_geoip\_lookup\_failure when I haven't specified it?

It is used i a diiferent .conf file for WinLogBeat.

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [December 17, 2017, 2:10am UTC](https://discuss.elastic.co/t/geoip-lookup-failure-but-not-specified/111348/2 "2017-12-17T02:10:10Z")

</div>

@teejayuu The fields seem to come from Logstash. Should I move your topic to LS forum?

---

<div class="post-metadata">

**Author:** ![teejayuu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/teejayuu/32/18356_2.png) [@teejayuu](https://discuss.elastic.co/u/teejayuu)\
**Post date:** [December 18, 2017, 9:40am UTC](https://discuss.elastic.co/t/geoip-lookup-failure-but-not-specified/111348/3 "2017-12-18T09:40:49Z")

</div>

Sorry. Can you move it to the correct place.  
Thanks

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [December 20, 2017, 12:48am UTC](https://discuss.elastic.co/t/geoip-lookup-failure-but-not-specified/111348/4 "2017-12-20T00:48:59Z")

</div>

Just moved it to LS

---

<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:** [January 17, 2018, 12:49am UTC](https://discuss.elastic.co/t/geoip-lookup-failure-but-not-specified/111348/5 "2018-01-17T00:49:29Z")

</div>

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