File tree Expand file tree Collapse file tree 1 file changed +9
-0
lines changed Expand file tree Collapse file tree 1 file changed +9
-0
lines changed Original file line number Diff line number Diff line change @@ -86,7 +86,9 @@ All nested logstash fields will be mapped to riemann fields containing all paren
86
86
separated by dots and the deepest value.
87
87
88
88
As an example, the logstash event:
89
+
89
90
[source,ruby]
91
+ -----
90
92
{
91
93
"@timestamp":"2013-12-10T14:36:26.151+0000",
92
94
"@version": 1,
@@ -96,14 +98,19 @@ As an example, the logstash event:
96
98
"key": "value"
97
99
}
98
100
}
101
+ -----
102
+
99
103
Is mapped to this riemann event:
104
+
100
105
[source,ruby]
106
+ -----
101
107
{
102
108
:time 1386686186,
103
109
:host host.domain.com,
104
110
:message log message,
105
111
:nested_field.key value
106
112
}
113
+ -----
107
114
108
115
It can be used in conjunction with or independent of the riemann_event option.
109
116
When used with the riemann_event any duplicate keys receive their value from
@@ -150,12 +157,14 @@ Any other field set here will be passed to Riemann as an event attribute.
150
157
151
158
Example:
152
159
[source,ruby]
160
+ -----
153
161
riemann {
154
162
riemann_event => {
155
163
"metric" => "%{metric}"
156
164
"service" => "%{service}"
157
165
}
158
166
}
167
+ -----
159
168
160
169
`metric` and `ttl` values will be coerced to a floating point value.
161
170
Values which cannot be coerced will zero (0.0).
You can’t perform that action at this time.
0 commit comments