Log processing data types
powered by Grail
The script in a processor definition operates with strongly typed data: the functions and operators accept only declared types of data. The type is assigned to all input fields defined by the
USING command as well as to the variables created while parsing or using the casting functions.
Whatever type has a field that is a part of the processor output, the system makes its best effort to convert it to a type expected by the event. The same applies to the input fields defined by the
USING command. For example, a
STRING attribute with the value
123 can be easily converted to the
INTEGER type, but not to the
Data types supported by the
USING command (processor input/output):
Has only two possible values: true and false.
A 32-bit signed two's complement integer that has a minimum value of
A 64-bit two's complement integer. The signed long has a minimum value of
A double-precision 64-bit IEEE 754 floating point. The range of its values is beyond the scope of this discussion, but is specified in the Floating-Point Types, Formats, and Values section of the Java Language Specification.
A time period in nanoseconds.
A sequence of characters with a specified character set.
A reference to a point in time with a precision of nanoseconds.
Represents an IPv4 or IPv6 address.
Additionally, within the processor script itself, more data types may appear after parsing:
An sequence of bytes.
A set of key-value pair data whose value can be any of supported data types.
A data type evaluated dynamically at runtime.
An array of
A set of key-value pairs with