Events-csv User Manual: Difference between revisions
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
"csv" assumes that the input file or piped content is text comma-separated content and parses it, generating [[Events-api_Concepts#Event|events]], which then are | "csv" assumes that the input file or piped content is text comma-separated content and parses it, generating [[Events-api_Concepts#Event|events]], which then are optionally filtered by the query and processed depending on the command specified on command line. | ||
csv [''[[#Commands|command]]''] [''[[Events-api_Concepts#Query|query]]''] <input-file.csv> | csv [''[[#Commands|command]]''] [''[[Events-api_Concepts#Query|query]]''] <input-file.csv> |
Revision as of 17:13, 22 September 2017
Internal
Overview
"csv" assumes that the input file or piped content is text comma-separated content and parses it, generating events, which then are optionally filtered by the query and processed depending on the command specified on command line.
csv [command] [query] <input-file.csv>
The default command, which does not need to be specified is output: the CSV content is parsed and the resulted events are displayed at stdout:
csv [query] [-o output-spec] <input-file.csv>
Usage on pipes:
tail -f input.csv | csv [command] [query]
Concepts
Commands
output
headers
Scan the CSV stream and display the headers, as they are identified in the stream. The command displays the number of the line on which the header is found, and then, for each header:
- the index that can be used to access the value that corresponds the header in a data lines. The index can be used for index-based output
- the header name
- the header type
- optionally, the header format
csv headers ./sample.csv line 1 header: 1: timestamp(time:MM/dd/yy HH:mm:ss) 2: CPU User Time(string) 3: CPU Kernel Time(string) 4: CPU I/O Wait Time(string)