Skip to content

Commit f15e8b3

Browse files
committed
Fix formatting for code samples in output-riemann
Fixes #774
1 parent 0f8106d commit f15e8b3

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

docs/plugins/outputs/riemann.asciidoc

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,9 @@ All nested logstash fields will be mapped to riemann fields containing all paren
8787
separated by dots and the deepest value.
8888

8989
As an example, the logstash event:
90+
9091
[source,ruby]
92+
-----
9193
{
9294
"@timestamp":"2013-12-10T14:36:26.151+0000",
9395
"@version": 1,
@@ -97,14 +99,19 @@ As an example, the logstash event:
9799
"key": "value"
98100
}
99101
}
102+
-----
103+
100104
Is mapped to this riemann event:
105+
101106
[source,ruby]
107+
-----
102108
{
103109
:time 1386686186,
104110
:host host.domain.com,
105111
:message log message,
106112
:nested_field.key value
107113
}
114+
-----
108115

109116
It can be used in conjunction with or independent of the riemann_event option.
110117
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.
151158

152159
Example:
153160
[source,ruby]
161+
-----
154162
riemann {
155163
riemann_event => {
156164
"metric" => "%{metric}"
157165
"service" => "%{service}"
158166
}
159167
}
168+
-----
160169

161170
`metric` and `ttl` values will be coerced to a floating point value.
162171
Values which cannot be coerced will zero (0.0).

0 commit comments

Comments
 (0)