Events User Manual - CSV Support

From NovaOrdis Knowledge Base
Revision as of 01:16, 5 November 2016 by Ovidiu (talk | contribs) (Ovidiu moved page Events User Manual - CSV Supports to Events User Manual - CSV Support without leaving a redirect)
Jump to navigation Jump to search

Internal

CSV Input Format: --------------------------------------------------------------------------------

The CSV input format consists in comma separated header names, with optional type and format information. If not type or format information are specified, the input fields are handled as strings. The general syntax is:

 <field-name>(<type>[:format])

If a value contains commas, it must be enclosed in double quotes to be parsed correctly, otherwise the parser will interpret comma as a field separator.

Examples: ----------------------------------------------------------------------------------------

 path - the content of the field be read verbatim and handled as string.
 timestamp(time:yy/MM/dd HH:mm:ss,SSS) - the content of the field will be parsed as time
 information according to the format specified between (time:...). The format follows Java
 SimpleDateFormat conventions. If the content cannot be converted into a time stamp, a FaultEvent
 will be generated and sent down the pipeline. For more details see:
 http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html
 status-code(int) - the content of the field will be interpreted as integer and parsed
 accordingly. If the content cannot be converted to an integer, a FaultEvent will be generated
 and sent down the pipeline.
 body-size(long) - the content of the field will be interpreted as long and parsed accordingly.
 If the content cannot be converted to a long, a FaultEvent will be generated and sent down the
 pipeline.