/opt/ardexa/logs. In order to collect data, a few rules must be followed.
/opt/ardexa/logsto identify the table and source. It is allowable to have more than 1 sub-directory for the source definition. So in the following example, are all allowable:
latest.csv(as per the above definition in the YAML file), the Ardexa agent will look in these files for data. Note that you can store any number of files in any of the Dynamic Configuration directories. If they are not named
latest.csvthen all files will be ignored by the agent. Only one
latest.csvfile per directory is allowed. The
latest.csvmust be formatted as shown in the example below:
datedefines date value. It MUST be ISO8601/RFC3339 compliant date and time plus timezone offset, e.g.
decimalany number with a fractional component
integerdefines any whole number. The value cannot have a decimal/fractional component
booldefines a boolean value.
false(case insensitive) are False, any other value is true
keyworddefines a fixed string , usually chosen from a small pool of choices, e.g. OK, RUNNING, ERROR, etc, which can contain any characters. If commas need to be included, they must be enclosed in quotes. If expect is not defined, then this will be used as the default.
log: unstructured text. Good for things like "comment" fields
discard: this field will not be sent to the cloud
latest.csvfile is not formatted according to the above, data will be rejected. If the number of values or the types does not match the header line, data will be rejected. The Ardexa cloud contains a table called
agent errors. This can be perused using SEARCHES to look for errors.