Skip to content

Fix formatting for code samples in output-riemann #774

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 3, 2019
Merged

Fix formatting for code samples in output-riemann #774

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/plugins/outputs/riemann.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,9 @@ All nested logstash fields will be mapped to riemann fields containing all paren
separated by dots and the deepest value.

As an example, the logstash event:

[source,ruby]
-----
{
"@timestamp":"2013-12-10T14:36:26.151+0000",
"@version": 1,
Expand All @@ -97,14 +99,19 @@ As an example, the logstash event:
"key": "value"
}
}
-----

Is mapped to this riemann event:

[source,ruby]
-----
{
:time 1386686186,
:host host.domain.com,
:message log message,
:nested_field.key value
}
-----

It can be used in conjunction with or independent of the riemann_event option.
When used with the riemann_event any duplicate keys receive their value from
Expand Down Expand Up @@ -151,12 +158,14 @@ Any other field set here will be passed to Riemann as an event attribute.

Example:
[source,ruby]
-----
riemann {
riemann_event => {
"metric" => "%{metric}"
"service" => "%{service}"
}
}
-----

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