logstash-filter-geoip 4.3.1-java → 5.0.0-java
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +2 -2
- data/docs/index.asciidoc +0 -22
- data/lib/logstash/filters/geoip.rb +1 -15
- data/logstash-filter-geoip.gemspec +1 -1
- data/vendor/GeoLite2-City.mmdb +0 -0
- data/vendor/jar-dependencies/org/logstash/filters/logstash-filter-geoip/4.2.0/logstash-filter-geoip-4.2.0.jar +0 -0
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: b51729b78c4efdfee230dea51aa3444295f3c4e3
|
4
|
+
data.tar.gz: 8d05b9fab90e0937f32b1b1d064fea992f73a1e7
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: dfd9679615064a2b7a9556c115aaac0a188a16fecdb7a4746284846ec667d1f51075ad917b06c4a9d16d41bfa4ebeed677693c6304db007da17267314bc16290
|
7
|
+
data.tar.gz: 64f1464722dacc2b9a2fd34099d7a9f4cfc78a449f27210134f534a1b292ca11f0f175c99418c9a7b62169487ae83008390b14d8d122ba71384a49b29e468a4e
|
data/CHANGELOG.md
CHANGED
data/docs/index.asciidoc
CHANGED
@@ -142,28 +142,6 @@ For the built-in GeoLite2 City database, the following are available:
|
|
142
142
|
`city_name`, `continent_code`, `country_code2`, `country_code3`, `country_name`,
|
143
143
|
`dma_code`, `ip`, `latitude`, `longitude`, `postal_code`, `region_name` and `timezone`.
|
144
144
|
|
145
|
-
[id="plugins-{type}s-{plugin}-lru_cache_size"]
|
146
|
-
===== `lru_cache_size` (DEPRECATED)
|
147
|
-
|
148
|
-
* DEPRECATED WARNING: This configuration item is deprecated and may not be available in future versions.
|
149
|
-
* Value type is <<number,number>>
|
150
|
-
* Default value is `1000`
|
151
|
-
|
152
|
-
GeoIP lookup is surprisingly expensive. This filter uses an LRU cache to take advantage of the fact that
|
153
|
-
IPs agents are often found adjacent to one another in log files and rarely have a random distribution.
|
154
|
-
The higher you set this the more likely an item is to be in the cache and the faster this filter will run.
|
155
|
-
However, if you set this too high you can use more memory than desired.
|
156
|
-
|
157
|
-
Experiment with different values for this option to find the best performance for your dataset.
|
158
|
-
|
159
|
-
This MUST be set to a value > 0. There is really no reason to not want this behavior, the overhead is minimal
|
160
|
-
and the speed gains are large.
|
161
|
-
|
162
|
-
It is important to note that this config value is global to the geoip_type. That is to say all instances of the geoip filter
|
163
|
-
of the same geoip_type share the same cache. The last declared cache size will 'win'. The reason for this is that there would be no benefit
|
164
|
-
to having multiple caches for different instances at different points in the pipeline, that would just increase the
|
165
|
-
number of cache misses and waste memory.
|
166
|
-
|
167
145
|
[id="plugins-{type}s-{plugin}-source"]
|
168
146
|
===== `source`
|
169
147
|
|
@@ -85,21 +85,7 @@ class LogStash::Filters::GeoIP < LogStash::Filters::Base
|
|
85
85
|
# number of cache misses and waste memory.
|
86
86
|
config :cache_size, :validate => :number, :default => 1000
|
87
87
|
|
88
|
-
|
89
|
-
# IPs agents are often found adjacent to one another in log files and rarely have a random distribution.
|
90
|
-
# The higher you set this the more likely an item is to be in the cache and the faster this filter will run.
|
91
|
-
# However, if you set this too high you can use more memory than desired.
|
92
|
-
#
|
93
|
-
# Experiment with different values for this option to find the best performance for your dataset.
|
94
|
-
#
|
95
|
-
# This MUST be set to a value > 0. There is really no reason to not want this behavior, the overhead is minimal
|
96
|
-
# and the speed gains are large.
|
97
|
-
#
|
98
|
-
# It is important to note that this config value is global to the geoip_type. That is to say all instances of the geoip filter
|
99
|
-
# of the same geoip_type share the same cache. The last declared cache size will 'win'. The reason for this is that there would be no benefit
|
100
|
-
# to having multiple caches for different instances at different points in the pipeline, that would just increase the
|
101
|
-
# number of cache misses and waste memory.
|
102
|
-
config :lru_cache_size, :validate => :number, :default => 1000, :deprecated => "This field has been deprecated in favor of cache_size."
|
88
|
+
config :lru_cache_size, :validate => :number, :obsolete => "This field has been obsoleted in favor of cache_size."
|
103
89
|
|
104
90
|
# Tags the event on failure to look up geo information. This can be used in later analysis.
|
105
91
|
config :tag_on_failure, :validate => :array, :default => ["_geoip_lookup_failure"]
|
@@ -1,7 +1,7 @@
|
|
1
1
|
Gem::Specification.new do |s|
|
2
2
|
|
3
3
|
s.name = 'logstash-filter-geoip'
|
4
|
-
s.version = '
|
4
|
+
s.version = '5.0.0'
|
5
5
|
s.licenses = ['Apache License (2.0)']
|
6
6
|
s.summary = "$summary"
|
7
7
|
s.description = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program"
|
data/vendor/GeoLite2-City.mmdb
CHANGED
Binary file
|
Binary file
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: logstash-filter-geoip
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version:
|
4
|
+
version: 5.0.0
|
5
5
|
platform: java
|
6
6
|
authors:
|
7
7
|
- Elastic
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2017-08-
|
11
|
+
date: 2017-08-01 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|