fluent-plugin-geoip 1.0.0 → 1.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: d8ae0d73eec8f27ed950ce080d02d0ada455fdc7
-  data.tar.gz: 3e442d004f0e4852ea8b713749eedb1f05991eaa
+SHA256:
+  metadata.gz: 35bca82d01d71c2eed7db735cf4e2394e6af0ec420baa511cfe74431fd0c88c4
+  data.tar.gz: e15c7f9fec5855d0012d97a65d0aa170338a169229e65eea5baf798c4d2d2763
 SHA512:
-  metadata.gz: a026783f1b3578c27081c142dc4829cdda7ed0ec0be13867ee42e6052818fde41630154d8311fc63d52b6808213bec0caf84281006143cbc8f9845f96a3e01b6
-  data.tar.gz: 70836a38b6e1596ff5dcae93dda3961b67e7a16f4dd050b2ddaa7c33ff17df63475526e8baf2b8a8e103eb81cc250be029d0ed96d7388c871fcd7bfcd8e5f79e
+  metadata.gz: c67641b18a5254169fa4c0d0fa7b32e1612c2f65c6f7ebfd5afffeaaa7c1f5a1ffa1e77334e10a7f5cecf476e0dbd6b7d64f080d93894b4b0cf8f7c4092b141d
+  data.tar.gz: c7e7fa0d170d4f451f9666bf471a76b193a7f0e466403992b85cb6051bc72b1a94e6f54ffe378cc5414d8cdf251a02402fa26c01507e58baf2b2db313690e4d3

data/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,19 @@
+#### Problem
+
+...
+
+#### Steps to replicate
+
+Provide example config and message
+
+#### Expected Behavior
+
+...
+
+#### Your environment
+
+* OS version
+* paste result of ``fluentd --version`` or ``td-agent --version``
+* plugin version
+  * paste boot log of fluentd or td-agent
+  * paste result of ``fluent-gem list``, ``td-agent-gem list`` or your Gemfile.lock

data/.travis.yml

@@ -4,7 +4,7 @@ services:
 
 env:
   global:
-    DOCKER_COMPOSE_VERSION: 1.8.1
+    DOCKER_COMPOSE_VERSION: 1.18.0
   matrix:
     - TARGET_RUBY_VERSION=2.1 BUNDLE_GEMFILE=/app/gemfiles/fluentd_v1.0_with_backport_dig.gemfile
     - TARGET_RUBY_VERSION=2.2 BUNDLE_GEMFILE=/app/gemfiles/fluentd_v1.0_with_backport_dig.gemfile

data/README.md

@@ -1,8 +1,8 @@
 # fluent-plugin-geoip [![Build Status](https://travis-ci.org/y-ken/fluent-plugin-geoip.png?branch=master)](https://travis-ci.org/y-ken/fluent-plugin-geoip)
 
-Fluentd Output plugin to add information about geographical location of IP addresses with Maxmind GeoIP databases.
+Fluentd Filter plugin to add information about geographical location of IP addresses with Maxmind GeoIP databases.
 
-fluent-plugin-geoip has bundled cost-free [GeoLite City database](http://dev.maxmind.com/geoip/legacy/geolite/) by default.<br />
+fluent-plugin-geoip has bundled cost-free [GeoLite2 Free Downloadable Databases](https://dev.maxmind.com/geoip/geoip2/geolite2/) and [GeoLite City database](http://dev.maxmind.com/geoip/legacy/geolite/) by default.<br />
 Also you can use purchased [GeoIP City database](http://www.maxmind.com/en/city) ([lang:ja](http://www.maxmind.com/ja/city)) which costs starting from $50.
 
 The accuracy details for GeoLite City (free) and GeoIP City (purchased) has described at the page below.
@@ -21,56 +21,7 @@ If you want to use this plugin with Fluentd v0.12.x or earlier use 0.8.x.
 
 ### Compatibility notice
 
-We've used Fluentd v1 API in this plugin since 1.0.0.
-So we have dropped some features.
-
-See also [official document](http://docs.fluentd.org/v1.0/articles/plugin-update-from-v12)
-
-#### Fluent::Mixin::RewriteTagName
-
-* `${tag}`, `__TAG__`
-
-    Alternative: Use `${tag}` placeholder
-
-* `${tag_parts[n]}`, `__TAG_PARTS[n]__`
-
-    Alternative: Use `${tag[n]}` placeholder
-
-* `${hostname}`, `__HOSTNAME__`
-
-    Alternative1: Use filter before this plugin and chunk keys:
-    ```
-    <filter>
-      @type record_transformer
-      <record>
-        hostname ${hostname}
-      </record>
-    </filter>
-    <match **>
-      @type geoip
-      tag geoip.${tag[1]}.${hostname}
-      <record>
-        city ${city["host"]}
-      </record>
-      <buffer tag, hostname>
-        flush_interval 1s
-      </buffer>
-    </match>
-    ```
-
-    Alternative2: Just inject hostname into record you can use `<inject>` section instead:
-    ```
-    <match **>
-      @type geoip
-      tag geoip.${tag[1]}.${hostname}
-      <record>
-        city ${city["host"]}
-      </record>
-      <inject>
-        hostname_key hostname
-      </inject>
-    </match>
-    ```
+We've removed GeoipOutput since 1.3.0, because GeoipFilter is enough to add information about geographical location of IP addresse.
 
 ## Dependency
 
@@ -78,18 +29,22 @@ before use, install dependent library as:
 
 ```bash
 # for RHEL/CentOS
-$ sudo yum group install "Development Tools"
+$ sudo yum groupinstall "Development Tools"
 $ sudo yum install geoip-devel --enablerepo=epel
+$ sudo yum install libmaxminddb-devel
 
 # for Ubuntu/Debian
 $ sudo apt-get install build-essential
 $ sudo apt-get install libgeoip-dev
+$ sudo apt-get install libmaxminddb-dev
 
 # for OS X
 $ brew install geoip
 $ bundle config build.geoip-c --with-geoip-dir=/usr/local/include/
 ```
 
+See [geoip2_c](https://github.com/okkez/geoip2_c#build-requirements), if you failed to install geoip2_c.
+
 ## Installation
 
 install with `gem` or td-agent provided command as:
@@ -107,201 +62,185 @@ $ sudo td-agent-gem install fluent-plugin-geoip
 
 ## Usage
 
-### For GeoipOutput
+### For GeoipFilter
+
+Note that filter version of geoip plugin does not have handling tag feature.
 
 ```xml
-<match access.apache>
+<filter access.apache>
   @type geoip
 
   # Specify one or more geoip lookup field which has ip address (default: host)
-  # in the case of accessing nested value, delimit keys by dot like 'host.ip'.
-  geoip_lookup_key  host
+  geoip_lookup_keys host
 
   # Specify optional geoip database (using bundled GeoLiteCity databse by default)
-  geoip_database    "/path/to/your/GeoIPCity.dat"
+  # geoip_database    "/path/to/your/GeoIPCity.dat"
   # Specify optional geoip2 database
-  # geoip2_database   "/path/to/your/GeoLite2-City.mmdb"
-  # Specify backend library (geoip, geoip2_compat, geoip2_c)
-  backend_library geoip
+  # geoip2_database   "/path/to/your/GeoLite2-City.mmdb" (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.)
   <record>
-    latitude        ${latitude["host"]}
-    longitude       ${longitude["host"]}
-    country_code3   ${country_code3["host"]}
-    country         ${country_code["host"]}
-    country_name    ${country_name["host"]}
-    dma             ${dma_code["host"]}
-    area            ${area_code["host"]}
-    region          ${region["host"]}
-    city            ${city["host"]}
+    city            ${city.names.en["host"]}
+    latitude        ${location.latitude["host"]}
+    longitude       ${location.longitude["host"]}
+    country         ${country.iso_code["host"]}
+    country_name    ${country.names.en["host"]}
+    postal_code     ${postal.code["host"]}
   </record>
 
-  # Settings for tag
-  tag               geoip.${tag[1]}
-
   # To avoid get stacktrace error with `[null, null]` array for elasticsearch.
   skip_adding_null_record  true
 
-  # Set log_level for fluentd-v0.10.43 or earlier (default: warn)
-  log_level         info
-
-  <buffer tag>
-    # Set buffering time (default: 0s)
-    flush_interval    1s
-  </buffer>
-</match>
+  # Set @log_level (default: warn)
+  @log_level         info
+</filter>
 ```
 
 #### Tips: how to geolocate multiple key
 
 ```xml
-<match access.apache>
+<filter access.apache>
   @type geoip
-  geoip_lookup_key  user1_host, user2_host
+  geoip_lookup_keys user1_host, user2_host
   <record>
-    user1_city      ${city["user1_host"]}
-    user2_city      ${city["user2_host"]}
+    user1_city      ${city.names.en["user1_host"]}
+    user2_city      ${city.names.en["user2_host"]}
   </record>
-  tag               geoip.${tag[1]}
-</match>
+</filter>
+```
+
+#### Tips: Modify records without city information
+
+```
+<filter access.apache>
+  @type geoip
+  geoip_lookup_keys remote_addr
+  <record>
+    city         ${city.names.en["remote_addr"]}     # skip adding fields if this field is null
+    latitude     ${location.latitude["remote_addr"]}
+    longitude    ${location.longitude["remote_addr"]}
+    country      ${country.iso_code["remote_addr"]}
+    country_name ${country.names.en["remote_addr"]}
+    postal_code  ${postal.code["remote_addr"]}
+  </record>
+  skip_adding_null_record true
+</filter>
+```
+
+Skip adding fields if incoming `remote_addr`'s GeoIP data is like following:
+
+```ruby
+# the record does not have "city" field
+{"continent"=>
+  {"code"=>"NA",
+   "geoname_id"=>6255149,
+   "names"=>
+    {"de"=>"Nordamerika",
+     "en"=>"North America",
+     "es"=>"Norteamérica",
+     "fr"=>"Amérique du Nord",
+     "ja"=>"北アメリカ",
+     "pt-BR"=>"América do Norte",
+     "ru"=>"Северная Америка",
+     "zh-CN"=>"北美洲"}},
+ "country"=>
+  {"geoname_id"=>6252001,
+   "iso_code"=>"US",
+   "names"=>
+    {"de"=>"USA",
+     "en"=>"United States",
+     "es"=>"Estados Unidos",
+     "fr"=>"États-Unis",
+     "ja"=>"アメリカ合衆国",
+     "pt-BR"=>"Estados Unidos",
+     "ru"=>"США",
+     "zh-CN"=>"美国"}},
+ "location"=>
+  {"accuracy_radius"=>1000, "latitude"=>37.751, "longitude"=>-97.822},
+ "registered_country"=>
+  {"geoname_id"=>6252001,
+   "iso_code"=>"US",
+   "names"=>
+    {"de"=>"USA",
+     "en"=>"United States",
+     "es"=>"Estados Unidos",
+     "fr"=>"États-Unis",
+     "ja"=>"アメリカ合衆国",
+     "pt-BR"=>"Estados Unidos",
+     "ru"=>"США",
+     "zh-CN"=>"美国"}}}
+```
+
+We can avoid this behavior changing field order in `<record>` like following:
+
+```
+<filter access.apache>
+  @type geoip
+  geoip_lookup_keys remote_addr
+  <record>
+    latitude     ${location.latitude["remote_addr"]} # this field must not be null
+    longitude    ${location.longitude["remote_addr"]}
+    country      ${country.iso_code["remote_addr"]}
+    country_name ${country.names.en["remote_addr"]}
+    postal_code  ${postal.code["remote_addr"]}
+    city         ${city.names.en["remote_addr"]}     # adding fields even if this field is null
+  </record>
+  skip_adding_null_record true
+</filter>
 ```
 
+#### Tips: nested attributes for geoip_lookup_keys
+
+See [Record Accessor Plugin Helper](https://docs.fluentd.org/plugin-helper-overview/api-plugin-helper-record_accessor)
+
+**NOTE** Since v1.3.0 does not interpret `host.ip` as nested attribute.
+
 #### Advanced config samples
 
 It is a sample to get friendly geo point recdords for elasticsearch with Yajl (JSON) parser.<br />
 
-**Notice** v0 config will be deprecated in the future.
-
 ```
-<match access.apache>
+<filter access.apache>
   @type                  geoip
-  geoip_lookup_key       host
+  geoip_lookup_keys      host
   <record>
     # lat lon as properties
     # ex. {"lat" => 37.4192008972168, "lon" => -122.05740356445312 }
-    location_properties  '{ "lat" : ${latitude["host"]}, "lon" : ${longitude["host"]} }'
+    location_properties  '{ "lat" : ${location.latitude["host"]}, "lon" : ${location.longitude["host"]} }'
   
     # lat lon as string
     # ex. "37.4192008972168,-122.05740356445312"
-    location_string      ${latitude["host"]},${longitude["host"]}
+    location_string      ${location.latitude["host"]},${location.longitude["host"]}
     
     # GeoJSON (lat lon as array) is useful for Kibana's bettermap.
     # ex. [-122.05740356445312, 37.4192008972168]
-    location_array       '[${longitude["host"]},${latitude["host"]}]'
+    location_array       '[${location.longitude["host"]},${location.latitude["host"]}]'
   </record>
-  tag                    geoip.${tag[1]}
 
   # To avoid get stacktrace error with `[null, null]` array for elasticsearch.
   skip_adding_null_record  true
-</match>
+</filter>
 ```
 
 On the case of using td-agent3 (v1-config), it have to quote `{ ... }` or `[ ... ]` block with quotation like below.
 
 ```
-<match access.apache>
-  @type                  geoip
-  geoip_lookup_key       host
-  <record>
-    location_properties  '{ "lat" : ${latitude["host"]}, "lon" : ${longitude["host"]} }'
-    location_string      ${latitude["host"]},${longitude["host"]}
-    location_array       '[${longitude["host"]},${latitude["host"]}]'
-  </record>
-  remove_tag_prefix      access.
-  tag                    geoip.${tag}
-  skip_adding_null_record  true
-</match>
-```
-
-### For GeoipFilter
-
-Note that filter version of geoip plugin does not have handling tag feature.
-
-```xml
 <filter access.apache>
-  @type geoip
-
-  # Specify one or more geoip lookup field which has ip address (default: host)
-  # in the case of accessing nested value, delimit keys by dot like 'host.ip'.
-  geoip_lookup_key  host
-
-  # Specify optional geoip database (using bundled GeoLiteCity databse by default)
-  geoip_database    "/path/to/your/GeoIPCity.dat"
-  # Specify optional geoip2 database
-  # geoip2_database   "/path/to/your/GeoLite2-City.mmdb"
-  # Specify backend library (geoip, geoip2_compat, geoip2_c)
-  backend_library geoip
-
-  # Set adding field with placeholder (more than one settings are required.)
+  @type                  geoip
+  geoip_lookup_keys      host
   <record>
-    city            ${city["host"]}
-    latitude        ${latitude["host"]}
-    longitude       ${longitude["host"]}
-    country_code3   ${country_code3["host"]}
-    country         ${country_code["host"]}
-    country_name    ${country_name["host"]}
-    dma             ${dma_code["host"]}
-    area            ${area_code["host"]}
-    region          ${region["host"]}
+    location_properties  '{ "lat" : ${location.latitude["host"]}, "lon" : ${location.longitude["host"]} }'
+    location_string      ${location.latitude["host"]},${location.longitude["host"]}
+    location_array       '[${location.longitude["host"]},${location.latitude["host"]}]'
   </record>
-
-  # To avoid get stacktrace error with `[null, null]` array for elasticsearch.
   skip_adding_null_record  true
-
-  # Set log_level for fluentd-v0.10.43 or earlier (default: warn)
-  log_level         info
 </filter>
 ```
 
 ## Tutorial
 
-### For GeoipOutput
-
-#### configuration
-
-```xml
-<source>
-  @type forward
-</source>
-
-<match test.geoip>
-  @type copy
-  <store>
-    @type stdout
-  </store>
-  <store>
-    @type    geoip
-    geoip_lookup_key  host
-    <record>
-      lat     ${latitude["host"]}
-      lon     ${longitude["host"]}
-      country ${country_code["host"]}
-    </record>
-    tag     debug.${tag[1]}
-  </store>
-</match>
-
-<match debug.**>
-  @type stdout
-</match>
-```
-
-#### result
-
-```bash
-# forward record with Google's ip address.
-$ echo '{"host":"66.102.9.80","message":"test"}' | fluent-cat test.geoip
-
-# check the result at stdout
-$ tail /var/log/td-agent/td-agent.log
-2013-08-04 16:21:32 +0900 test.geoip: {"host":"66.102.9.80","message":"test"}
-2013-08-04 16:21:32 +0900 debug.geoip: {"host":"66.102.9.80","message":"test","lat":37.4192008972168,"lon":-122.05740356445312,"country":"US"}
-```
-
-For more details of geoip data format is described at the page below in section `GeoIP City Edition CSV Database Fields`.<br />
-http://dev.maxmind.com/geoip/legacy/csv/
-
 ### For GeoipFilter
 
 #### configuration
@@ -313,11 +252,11 @@ http://dev.maxmind.com/geoip/legacy/csv/
 
 <filter test.geoip>
   @type    geoip
-  geoip_lookup_key  host
+  geoip_lookup_keys  host
   <record>
-    city  ${city["host"]}
-    lat   ${latitude["host"]}
-    lon   ${longitude["host"]}
+    city  ${city.names.en["host"]}
+    lat   ${location.latitude["host"]}
+    lon   ${location.longitude["host"]}
   </record>
 </filter>
 
@@ -337,34 +276,15 @@ $ tail /var/log/td-agent/td-agent.log
 2016-02-01 12:04:37 +0900 test.geoip: {"host":"66.102.9.80","message":"test","city":"Mountain View","lat":37.4192008972168,"lon":-122.05740356445312}
 ```
 
-For more details of geoip data format is described at the page below in section `GeoIP City Edition CSV Database Fields`.<br />
-http://dev.maxmind.com/geoip/legacy/csv/
-
-## Placeholders
-
-### GeoIP legacy
-
-Provides these placeholders for adding field of geolocate results.<br />
-For more example of geolocating, you can try these websites like [Geo IP Address View](http://www.geoipview.com/) or [View my IP information](http://www.geoiptool.com/en/).
-
-| placeholder attributes         | output example    | type         | note |
-|--------------------------------|-------------------|--------------|------|
-| ${city[lookup_field]}          | "Ithaca"          | varchar(255) |  -   |
-| ${latitude[lookup_field]}      | 42.4277992248535  | decimal      |  -   |
-| ${longitude[lookup_field]}     | -76.4981994628906 | decimal      |  -   |
-| ${country_code3[lookup_field]} | "USA"             | varchar(3)   |  -   |
-| ${country_code[lookup_field]}  | "US"              | varchar(2)   | A two-character ISO 3166-1 country code      |
-| ${country_name[lookup_field]}  | "United States"   | varchar(50)  |  -   |
-| ${dma_code[lookup_field]}      | 555               | unsigned int | **only for US**  |
-| ${area_code[lookup_field]}     | 607               | char(3)      | **only for US**  |
-| ${region[lookup_field]}        | "NY"              | char(2)      | A two character ISO-3166-2 or FIPS 10-4 code |
-
-Further more specification available at http://dev.maxmind.com/geoip/legacy/csv/#GeoIP_City_Edition_CSV_Database_Fields
+You can check geoip data format using [utils/dump.rb](https://github.com/okkez/fluent-plugin-geoip/utils/dump.rb).
 
-Related configurations:
+```
+$ bundle exec ruby urils/dump.rb geoip2 66.102.3.80
+$ bundle exec ruby urils/dump.rb geoip2_compat 66.102.3.80
+$ bundle exec ruby urils/dump.rb geoip 66.102.3.80
+```
 
-* `backend_library`: `geoip` (default)
-* `geoip_database`: path to your GeoLiteCity.dat
+## Placeholders
 
 ### GeoIP2
 
@@ -405,43 +325,89 @@ Related configurations:
 * `backend_library`: `geoip2_compat` or `geoip2_c`
 * `geoip2_database`: path to your GeoLite2-City.mmdb
 
+### GeoIP legacy
+
+Provides these placeholders for adding field of geolocate results.<br />
+For more example of geolocating, you can try these websites like [Geo IP Address View](http://www.geoipview.com/) or [View my IP information](http://www.geoiptool.com/en/).
+
+| placeholder attributes         | output example    | type         | note |
+|--------------------------------|-------------------|--------------|------|
+| ${city[lookup_field]}          | "Ithaca"          | varchar(255) |  -   |
+| ${latitude[lookup_field]}      | 42.4277992248535  | decimal      |  -   |
+| ${longitude[lookup_field]}     | -76.4981994628906 | decimal      |  -   |
+| ${country_code3[lookup_field]} | "USA"             | varchar(3)   |  -   |
+| ${country_code[lookup_field]}  | "US"              | varchar(2)   | A two-character ISO 3166-1 country code      |
+| ${country_name[lookup_field]}  | "United States"   | varchar(50)  |  -   |
+| ${dma_code[lookup_field]}      | 555               | unsigned int | **only for US**  |
+| ${area_code[lookup_field]}     | 607               | char(3)      | **only for US**  |
+| ${region[lookup_field]}        | "NY"              | char(2)      | A two character ISO-3166-2 or FIPS 10-4 code |
+
+Further more specification available at http://dev.maxmind.com/geoip/legacy/csv/#GeoIP_City_Edition_CSV_Database_Fields
+
+Related configurations:
+
+* `backend_library`: `geoip` (default)
+* `geoip_database`: path to your GeoLiteCity.dat
+
 ## Parameters
 
-### GeoipOutput
+### GeoipFilter
 
-* `include_tag_key` (default: false)
-* `tag_key`
+Note that filter version of `geoip` plugin does not have handling `tag` feature.
 
-Add original tag name into filtered record using SetTagKeyMixin.<br />
-Further details are written at http://docs.fluentd.org/articles/in_exec
+#### Plugin helpers
 
-* `skip_adding_null_record` (default: false)
+* [compat_parameters](https://docs.fluentd.org/plugin-helper-overview/api-plugin-helper-compat_parameters)
+* [inject](https://docs.fluentd.org/plugin-helper-overview/api-plugin-helper-inject)
 
-Skip adding geoip fields when this valaues to `true`.
-On the case of getting nothing of GeoIP info (such as local IP), it will output the original record without changing anything.
+See also [Filter Plugin Overview](https://docs.fluentd.org/filter)
 
-* `tag`
+#### Supported sections
 
-On using this option with tag placeholder like `tag geoip.${tag}` (test code is available at [test_out_geoip.rb](https://github.com/y-ken/fluent-plugin-geoip/blob/master/test/plugin/test_out_geoip.rb)).
+* [Inject section configurations](https://docs.fluentd.org/configuration/inject-section)
 
-* `flush_interval` (default: 0 sec)
+#### Parameters
 
-Set buffering time to execute bulk lookup geoip.
+[Plugin Common Paramteters](https://docs.fluentd.org/configuration/plugin-common-parameters)
 
-### GeoipFilter
+**geoip_database** (string) (optional)
 
-Note that filter version of `geoip` plugin does not have handling `tag` feature.
+* Default value: bundled database `GeoLiteCity.dat`
+
+Path to GeoIP database file.
+
+**geoip2_database** (string) (optional)
+
+* Default value: bundled database `GeoLite2-City.mmdb`.
+
+Path to GeoIP2 database file.
 
-* `include_tag_key` (default: false)
+**geoip_lookup_keys** (array) (optional)
 
-Add original tag name into filtered record using SetTagKeyMixin.<br />
-Further details are written at http://docs.fluentd.org/articles/in_exec
+* Default_value: `["host"]`
 
-* `skip_adding_null_record` (default: false)
+Specify one or more geoip lookup field which has IP address.
+
+**geoip_lookup_key** (string) (optional) (deprecated)
+
+* Default value: `nil`.
+
+Use geoip_lookup_keys instead.
+
+**skip_adding_null_record** (bool) (optional)
+
+* Default value: `nil`
 
 Skip adding geoip fields when this valaues to `true`.
 On the case of getting nothing of GeoIP info (such as local IP), it will output the original record without changing anything.
 
+**backend_library** (enum) (optional)
+
+* Available values: `geoip`, `geoip2_compat`, `geoip2_c`
+* Default value: `geoip2_c`.
+
+Set backend library.
+
 ## Articles
 
 * [IPアドレスを元に位置情報をリアルタイムに付与する fluent-plugin-geoip v0.0.1をリリースしました #fluentd - Y-Ken Studio](http://y-ken.hatenablog.com/entry/fluent-plugin-geoip-has-released)<br />
@@ -463,8 +429,6 @@ http://developer.smartnews.be/blog/2013/10/03/easy-data-analysis-using-fluentd-r
 
 Pull requests are very welcome!!
 
-* support [GeoIP2](http://dev.maxmind.com/geoip/geoip2/whats-new-in-geoip2/)
-
 ## Contributing
 
 1. Fork it