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