usage: import json [<parameters>] imports JSON with schema parameters: [-h | -? | --help] <boolean> prints the help text [--documentation?] <boolean> prints the Markdown-formatted documentation [-l | --listen] <string> the port number to listen on [-r | --read] <string> path to input where to read events from [-s | --schema-file] <string> path to alternate schema [-S | --schema] <string> alternate schema as string [-t | --type] <string> type the data should be parsed as [-d | --uds] <boolean> treat -r as listening UNIX domain socket
json import format consumes line-delimited
according to a specified schema. That is, one line corresponds to one event.
The object field names correspond to record field names.
JSON’s can express only a subset VAST’s data model. For example, VAST has first-class support IP addresses but JSON can only represent them as strings. To get the most out of your data, it is therefore important to define a schema to get a differentiated view of the data.
infer command also supports schema inference for JSON data. For example,
head data.json | vast infer will print a raw schema that can be supplied to
-s as file or to
-S as string. However, after
infer dumps the schema, the generic type name should still be adjusted and
this would be the time to annotate fields with additional attributes, such as