logstash-output-elasticsearch 10.2.0-java → 10.2.1-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 +3 -0
- data/docs/index.asciidoc +4 -3
- data/logstash-output-elasticsearch.gemspec +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 4145b5bbd50a648c7557370139f600af5d5d83f193bcdf3956608b48b1d9d493
|
|
4
|
+
data.tar.gz: ac2d97688a709878bf8283905bee2b146694c73362739e6f47804c65ee183337
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 6431afb36c0886342fc9930f931eaafca542d6c16c630082ad1acdb6603900cbc73652ef50248ec562b0192ca041604494167930254abf5f0d8412933132f7c8
|
|
7
|
+
data.tar.gz: f0b566a439e5e2a5ea9f6d0bf02a26853dcf8eb2879c00584ab0b58e20dc92139c7b479c4893c0a0ff608b484f6974046cc31e06187d056e3e7989dfe66a0ebd
|
data/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,6 @@
|
|
|
1
|
+
## 10.2.1
|
|
2
|
+
- Fixed wording and corrected option in documentation [#881](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/881) [#883](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/883)
|
|
3
|
+
|
|
1
4
|
## 10.2.0
|
|
2
5
|
- Deprecation: Added warning about connecting a default Distribution of Logstash with an OSS version of ES [#875](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/875)
|
|
3
6
|
- Added template for connecting to ES 8.x [#871](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/871)
|
data/docs/index.asciidoc
CHANGED
|
@@ -105,9 +105,10 @@ This feature requires an Elasticsearch instance of 6.6.0 or higher with at least
|
|
|
105
105
|
|
|
106
106
|
Logstash can use {ref}/index-lifecycle-management.html[Index Lifecycle Management] to automate the management of indices over time.
|
|
107
107
|
|
|
108
|
-
The use of Index Lifecycle Management is controlled by the `ilm_enabled`
|
|
109
|
-
|
|
110
|
-
|
|
108
|
+
The use of Index Lifecycle Management is controlled by the `ilm_enabled`
|
|
109
|
+
setting. By default, this setting detects whether the Elasticsearch instance
|
|
110
|
+
supports ILM, and uses it if it is available. `ilm_enabled` can also be set to
|
|
111
|
+
`true` or `false` to override the automatic detection, or disable ILM.
|
|
111
112
|
|
|
112
113
|
This will overwrite the index settings and adjust the Logstash template to write the necessary settings for the template
|
|
113
114
|
to support index lifecycle management, including the index policy and rollover alias to be used.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Gem::Specification.new do |s|
|
|
2
2
|
s.name = 'logstash-output-elasticsearch'
|
|
3
|
-
s.version = '10.2.
|
|
3
|
+
s.version = '10.2.1'
|
|
4
4
|
s.licenses = ['apache-2.0']
|
|
5
5
|
s.summary = "Stores logs in Elasticsearch"
|
|
6
6
|
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"
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: logstash-output-elasticsearch
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 10.2.
|
|
4
|
+
version: 10.2.1
|
|
5
5
|
platform: java
|
|
6
6
|
authors:
|
|
7
7
|
- Elastic
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2019-10-
|
|
11
|
+
date: 2019-10-09 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|