logstash-filter-mutate 3.3.3 → 3.3.4
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +4 -0
- data/docs/index.asciidoc +38 -0
- data/logstash-filter-mutate.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: 10c472383e1b7198e53fce13513fa010542a198cfdaf76dd617067538f4e0a94
|
4
|
+
data.tar.gz: bebff8caed3fe2d7949c386730ea7392f3c56f4d27395a0eaf8fb83b9c923fc7
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 4290aa84cce80d2b3c5f3b60fba4926d4f46db250609a3203874cfca77364d4c5979e3625ed8579294f1e75359d3e9c455e29ca76d29f4b913fa6a70bb4e7dcc
|
7
|
+
data.tar.gz: 6e3cb113ad72a0c0bdedcc50c6098d0fda4de7ad07fb44c55b7423f55acc1a8dcb7caf2e08d71d9b1d0cfc6150349b785599d6abbfca3a666c53ca2f3c3ba826
|
data/CHANGELOG.md
CHANGED
@@ -1,3 +1,7 @@
|
|
1
|
+
## 3.3.4
|
2
|
+
- Changed documentation to clarify execution order and to provide workaround
|
3
|
+
[#128](https://github.com/logstash-plugins/logstash-filter-mutate/pull/128)
|
4
|
+
|
1
5
|
## 3.3.3
|
2
6
|
- Changed documentation to clarify use of `replace` config option [#125](https://github.com/logstash-plugins/logstash-filter-mutate/pull/125)
|
3
7
|
|
data/docs/index.asciidoc
CHANGED
@@ -23,6 +23,44 @@ include::{include_path}/plugin_header.asciidoc[]
|
|
23
23
|
The mutate filter allows you to perform general mutations on fields. You
|
24
24
|
can rename, remove, replace, and modify fields in your events.
|
25
25
|
|
26
|
+
[id="plugins-{type}s-{plugin}-proc_order"]
|
27
|
+
===== Processing order
|
28
|
+
|
29
|
+
Mutations in a config file are executed in this order:
|
30
|
+
|
31
|
+
* coerce
|
32
|
+
* rename
|
33
|
+
* update
|
34
|
+
* replace
|
35
|
+
* convert
|
36
|
+
* gsub
|
37
|
+
* uppercase
|
38
|
+
* capitalize
|
39
|
+
* lowercase
|
40
|
+
* strip
|
41
|
+
* remove
|
42
|
+
* split
|
43
|
+
* join
|
44
|
+
* merge
|
45
|
+
* copy
|
46
|
+
|
47
|
+
You can control the order by using separate mutate blocks.
|
48
|
+
|
49
|
+
Example:
|
50
|
+
[source,ruby]
|
51
|
+
-----
|
52
|
+
filter {
|
53
|
+
mutate {
|
54
|
+
split => ["hostname", "."]
|
55
|
+
add_field => { "shortHostname" => "%{hostname[0]}" }
|
56
|
+
}
|
57
|
+
|
58
|
+
mutate {
|
59
|
+
rename => ["shortHostname", "hostname" ]
|
60
|
+
}
|
61
|
+
}
|
62
|
+
-----
|
63
|
+
|
26
64
|
[id="plugins-{type}s-{plugin}-options"]
|
27
65
|
==== Mutate Filter Configuration Options
|
28
66
|
|
@@ -1,7 +1,7 @@
|
|
1
1
|
Gem::Specification.new do |s|
|
2
2
|
|
3
3
|
s.name = 'logstash-filter-mutate'
|
4
|
-
s.version = '3.3.
|
4
|
+
s.version = '3.3.4'
|
5
5
|
s.licenses = ['Apache License (2.0)']
|
6
6
|
s.summary = "Performs mutations on fields"
|
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-filter-mutate
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 3.3.
|
4
|
+
version: 3.3.4
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Elastic
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2018-
|
11
|
+
date: 2018-10-19 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|