fluent-plugin-multi-format-parser 0.1.0 → 0.1.1
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 +4 -4
- data/README.md +19 -0
- data/VERSION +1 -1
- data/lib/fluent/plugin/parser_multi_format.rb +1 -0
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: b3ccd298b01b05ed96a4494b153bd4ee4abd2b8d
|
4
|
+
data.tar.gz: 5b8399121244fd4f5939a7acb8c2481c6450d1ce
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: fefc45c5044df050487e7189d0071ee6021c29cac9ba4383e91273a08bdbf9cea851cd29ce160eac99df3c9994a775e48eb62f0c1db63bbc157aadccd2a14f3d
|
7
|
+
data.tar.gz: 8a69a5e16b154f21961b7227ee6e55a8ee7945825a966cc2e2badf5cde8ba9b921d5f671485947795979449c095d05d50089a4df401b826ec25aa1288b20c9d9
|
data/README.md
CHANGED
@@ -35,6 +35,25 @@ Use multiple `<pattern>` to specify multiple format.
|
|
35
35
|
Available format patterns and parameters are depends on Fluentd parsers.
|
36
36
|
See [in_tail format document](http://docs.fluentd.org/articles/in_tail) for more details.
|
37
37
|
|
38
|
+
### For v0.14
|
39
|
+
|
40
|
+
This plugin handles `pattern` section manually, so v0.14's automatic parameter conversion doesn't work well.
|
41
|
+
If you want to use this plugin with v0.14, you need to use v0.14 parser syntax like below
|
42
|
+
|
43
|
+
<filter app.**>
|
44
|
+
@type parser
|
45
|
+
key_name message
|
46
|
+
<parse> # Use <parse> section for parser parameters
|
47
|
+
@type multi_format
|
48
|
+
<pattern>
|
49
|
+
format json
|
50
|
+
</pattern>
|
51
|
+
<pattern>
|
52
|
+
format none
|
53
|
+
</pattern>
|
54
|
+
</parse>
|
55
|
+
</filter>
|
56
|
+
|
38
57
|
### NOTE
|
39
58
|
|
40
59
|
This plugin doesn't work with `multiline` parsers because parser itself doesn't store previous lines.
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.1.
|
1
|
+
0.1.1
|