<p>I am running EFK using ECK 8.5.3. fluentd <code>ConfigMap</code>:</p>
<pre><code>      @type geoip
      # Specify one or more geoip lookup field which has ip address (default: host)
      geoip_lookup_keys IP

      # Specify optional geoip database (using bundled GeoLiteCity databse by default)
      # geoip_database    &quot;/path/to/your/GeoIPCity.dat&quot;
      # Specify optional geoip2 database
      # geoip2_database   &quot;/path/to/your/GeoLite2-City.mmdb&quot; (using bundled GeoLite2-City.mmdb by default)
      # Specify backend library (geoip2_c, geoip, geoip2_compat)
      backend_library geoip2_c

      # Set adding field with placeholder (more than one settings are required.)
     &lt;record&gt;
        city            ${city.names.en[&quot;IP&quot;]}
        latitude        ${location.latitude[&quot;IP&quot;]}
        longitude       ${location.longitude[&quot;IP&quot;]}
        country_code    ${country.iso_code[&quot;IP&quot;]}
        country_name    ${country.names.en[&quot;IP&quot;]}
        postal_code     ${postal.code[&quot;IP&quot;]}
        location_properties '{ &quot;lat&quot; : ${location.latitude[&quot;IP&quot;]}, &quot;lon&quot; : ${location.longitude[&quot;IP&quot;]} }'
        location_string     ${location.latitude[&quot;IP&quot;]},${location.longitude[&quot;IP&quot;]}
        location_array      '[${location.longitude[&quot;IP&quot;]},${location.latitude[&quot;IP&quot;]}]'
      &lt;/record&gt;      
</code></pre>
<p>ES template:</p>
<pre><code>      &quot;mappings&quot;: {
          &quot;properties&quot;: {
              &quot;location_properties&quot;: { &quot;type&quot;: &quot;geo_point&quot; },
              &quot;location_string&quot;: { &quot;type&quot;: &quot;geo_point&quot; },
              &quot;location_array&quot;: { &quot;type&quot;: &quot;geo_point&quot; }
          }
      }
</code></pre>
<p>I don't see any of the properties in Kibana ECK 8.5.3 at all. What do I miss?</p>

Kok How Teh
<p>The issue can be fixed by using JSON format string.</p>
<p>As mentioned in the <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/geo-point.html" rel="nofollow noreferrer">document</a>:</p>
<blockquote>
<p>As with geo_shape and point, geo_point can be specified in GeoJSON and
Well-Known Text formats. However, there are a number of additional
formats that are supported for convenience and historical reasons. In
total there are six ways that a geopoint may be specified.</p>
</blockquote>
<p>You can also refer to  this <a href="https://stackoverflow.com/questions/33132731/missing-geo-point-fields-in-elasticsearch-response">stack post</a> for more information.</p>
