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

CSV data input format (for use with exec, tail) #2108

Closed
stanch opened this issue Nov 30, 2016 · 3 comments · Fixed by #4439
Closed

CSV data input format (for use with exec, tail) #2108

stanch opened this issue Nov 30, 2016 · 3 comments · Fixed by #4439
Assignees
Labels
feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin
Milestone

Comments

@stanch
Copy link

stanch commented Nov 30, 2016

It would be great to have CSV among the supported data input formats. In particular, this allows to leverage the tail plugin to integrate with existing tools outputting CSV, instead of e.g. using a named pipe (see also: #2089) as an adapter.

According to the input format documentation, there are four components that need to be extracted:

  1. Measurement Name
  2. Tags
  3. Fields
  4. Timestamp

Here is the suggested configuration format that allows to map those to CSV columns:

# The new data format
data_format = "csv"
data_separator = ","
data_quote_char = "\""

# List of column names in the CSV, in order of appearance on each line
data_columns = [
  "ts",
  "system_id",
  "client_id",
  "request_type",
  "latency"
]

# The column containing the measurement name
name_column = "request_type"

# The column containing the timestamp
timestamp_column = "ts"

# List of columns containing tags
tag_columns = [
  "system_id",
  "client_id"
]

# List of columns containing fields
field_columns = [
  "latency"
]
@sparrc sparrc added this to the Future Milestone milestone Nov 30, 2016
@sparrc sparrc added the feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin label Nov 30, 2016
@danielnelson danielnelson removed this from the Future Milestone milestone Jun 14, 2017
@Rushi-Kumar
Copy link

Is it supported now??

@joeltstephen
Copy link

Hi @stanch, Is it supported now ?

@stanch
Copy link
Author

stanch commented Jan 11, 2018

@joeltstephen I am not a contributor, so I don’t know for sure, but the page I linked to in the original issue description still does not mention it, so I assume it’s not supported. I suggest you to look into https://github.com/influxdata/telegraf/tree/master/plugins/inputs/logparser, it might be an alternative solution.

@maxunt maxunt self-assigned this Jul 19, 2018
@maxunt maxunt mentioned this issue Jul 23, 2018
3 tasks
@russorat russorat added this to the 1.8.0 milestone Aug 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants