Skip to content
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.

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

Whitespace in field names with outputs.graphite #1637

Closed
kostasb opened this issue Aug 16, 2016 · 0 comments · Fixed by #1640
Closed

Whitespace in field names with outputs.graphite #1637

kostasb opened this issue Aug 16, 2016 · 0 comments · Fixed by #1640
Labels
bug unexpected problem or unintended behavior

Comments

@kostasb
Copy link

kostasb commented Aug 16, 2016

1.0-beta3

Field names that include a whitespace generate malformed output when using the Graphite format.

Example input:
ameasurement,atag=test a\ field="value"

Output in Line Protocol:
ameasurement,atag=test a\ field="value" 1471350314460772128

Output in Graphite format:
ameasurement.test.a field "value" 1471350314

Graphite messages are of the form:metric_path value timestamp\n
The metric path can not include a whitespace.

This is not an issue with tags because whitespaces in tag values are replaced with a "_" separator.

@sparrc A configurable separator to replace whitespaces in field names for the graphite output may be a solution.

@sparrc sparrc added the bug unexpected problem or unintended behavior label Aug 16, 2016
sparrc added a commit that referenced this issue Aug 17, 2016
also sanitize the names at a higher scope for better clarity

closes #1637
sparrc added a commit that referenced this issue Aug 17, 2016
also sanitize the names at a higher scope for better clarity

closes #1637
sparrc added a commit that referenced this issue Aug 17, 2016
also sanitize the names at a higher scope for better clarity

closes #1637
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants