Configuration parameters
Use the parameters in this section to configure the . The Telemetry Pipeline web interface uses the items in the Name column to describe these parameters. Pipeline configuration files use the items in the Key column as YAML keys.| Name | Key | Description | Default |
|---|---|---|---|
| Source key | src | Required. The key to store your original CSV log entry. Don’t change this setting from its default value. | log |
| Destination key | dst | Required. The key to store your transformed JSON data. Don’t change this setting from its default value. | decoded_csv |
| Parse header checkbox | parseHeader | Indicates whether the first entry in your CSV data contains headers. If selected, the decode CSV rule uses these headers as keys to store the values of subsequent rows of data. | Not selected |
| Preset header | header | A list of headers to use as keys for storing the values of each row’s data. Use a comma to separate the names of your headers, but don’t use spaces between each name. This list must contain the same number of headers as there are columns of data. For example, if your CSV logs contain seven columns of data, you must specify seven header names to use as keys. | none |
| Comment | comment | A custom note or description of the rule’s function. This text is displayed next to the rule’s name in the Actions list in the processing rules interface. | none |
If you enable both Parse header and Preset header, the Parse header
setting takes precedence. For best results, enable one setting at a time rather
than using both simultaneously.
Examples
Using the decode CSV rule lets you turn CSV-stored log data into a more traditional log format for storage and analysis.Without headers
If you don’t specify header information, this rule transforms CSV data into an array. For example, given this sample CSV data:log and the Destination key
value decoded_csv returns the following result:
log key and used the comma-separated
row values to create the decoded_csv array.
With preset headers
If you specify header information in the Preset header setting, CSV data becomes a series of key/value pairs. For example, given this sample CSV data:log, the Destination key
value decoded_csv, and the Preset header value time,user,page,result
returns the following result:
log key and assigned each row’s
comma-separated values to a series of key/value pairs in decoded_csv.
With parsed headers
If you enable the Parse header setting, CSV data becomes a series of key/value pairs with keys based on the parsed header row. For example, given this sample CSV data:log, the Destination key
value decoded_csv, and the Parse header value enabled returns the
following result:
log key, except for the row
that contained header names.