logstash-output-elasticsearch 5.3.3-java → 5.3.4-java
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: a1f874229a886c9f587b38cabaf35c3281ac82fc
|
4
|
+
data.tar.gz: db38f67eb52fbd4d64e11b5a4d1157ad10649ada
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 5a8a0d210003dc9e36f5a173caa085730e06e4fca6db70e39277d0b8094f75b0eba21aa138abe197dd0899bac61fa0af9862baee03288481302df2af0b036035
|
7
|
+
data.tar.gz: 48afb4e6a3f6be0a46c863df27f7401360808272cf04aef6b1af6d96b912b5a5e2ab58dc46c1c7d1178336a2f2a20dcf3b07cfb512e2122441c0aa1e8ce63458
|
data/CHANGELOG.md
CHANGED
@@ -16,15 +16,18 @@ module LogStash; module Outputs; class ElasticSearch
|
|
16
16
|
# otherwise the document type will be assigned the value of 'logs'
|
17
17
|
mod.config :document_type, :validate => :string
|
18
18
|
|
19
|
-
#
|
20
|
-
#
|
21
|
-
#
|
22
|
-
# `logstash-%{+YYYY.MM.dd}`
|
23
|
-
#
|
19
|
+
# From Logstash 1.3 onwards, a template is applied to Elasticsearch during
|
20
|
+
# Logstash's startup if one with the name `template_name` does not already exist.
|
21
|
+
# By default, the contents of this template is the default template for
|
22
|
+
# `logstash-%{+YYYY.MM.dd}` which always matches indices based on the pattern
|
23
|
+
# `logstash-*`. Should you require support for other index names, or would like
|
24
|
+
# to change the mappings in the template in general, a custom template can be
|
25
|
+
# specified by setting `template` to the path of a template file.
|
24
26
|
#
|
25
|
-
#
|
26
|
-
#
|
27
|
-
#
|
27
|
+
# Setting `manage_template` to false disables this feature. If you require more
|
28
|
+
# control over template creation, (e.g. creating indices dynamically based on
|
29
|
+
# field names) you should set `manage_template` to false and use the REST
|
30
|
+
# API to apply your templates manually.
|
28
31
|
mod.config :manage_template, :validate => :boolean, :default => true
|
29
32
|
|
30
33
|
# This configuration option defines how the template is named inside Elasticsearch.
|
@@ -137,7 +140,8 @@ module LogStash; module Outputs; class ElasticSearch
|
|
137
140
|
# for more info
|
138
141
|
mod.config :retry_on_conflict, :validate => :number, :default => 1
|
139
142
|
|
140
|
-
# Set which ingest pipeline you wish to execute for an event
|
143
|
+
# Set which ingest pipeline you wish to execute for an event. You can also use event dependent configuration
|
144
|
+
# here like `pipeline => "%{INGEST_PIPELINE}"`
|
141
145
|
mod.config :pipeline, :validate => :string, :default => nil
|
142
146
|
end
|
143
147
|
end
|
@@ -1,7 +1,7 @@
|
|
1
1
|
Gem::Specification.new do |s|
|
2
2
|
|
3
3
|
s.name = 'logstash-output-elasticsearch'
|
4
|
-
s.version = '5.3.
|
4
|
+
s.version = '5.3.4'
|
5
5
|
s.licenses = ['apache-2.0']
|
6
6
|
s.summary = "Logstash Output to Elasticsearch"
|
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"
|
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: 5.3.
|
4
|
+
version: 5.3.4
|
5
5
|
platform: java
|
6
6
|
authors:
|
7
7
|
- Elastic
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2016-11-
|
11
|
+
date: 2016-11-14 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|