Events-processing output

Internal

• events-processing

Overview

The default procedure applied to event streams, in absence of any other configuration. The procedure inspects the events and sends the events' string representation to the configured output stream, which is usually stdout. The procedure can be programmatically configured to use a different output stream.

The string representation for an event is generated according to the following algorithm:

• If no output format is explicitly specified by the command, the output procedure will inspect the event, and will try to use, in order:
  • the preferred representation of the event, as returned by the event.
  • the raw representation of the event, as returned by event.
  • for timed events, the timestamp.
  • the event's toString() invocation result.
• If an output format is specified, the output format will be used to render the event.

If a custom output format is used, and only In case of timed events, the leading timestamp will be generated regardless of the details of the custom output format. If the output format explicitly specified the timestamp, the timestamp will be redundantly rendered.

One way to provide the format specification is on command-line: format specification arguments follow the "-o" marker and end either with the last argument or when a higher level argument (file, for example) is encountered.The output format also acts as a filter - if the event does not match at least one of the output format elements, it will not be displayed at all. More details on the output format are available below: "Output Format".

some-parser [output] -o <output-format> ./file.txt

cat ./file.txt | some-parser [output] -o <output-format>

Output Format

The output format can be used to:

• Restrict the output to specific event properties.
• Restrict the output to specific event types.

Headers

The output procedure will display a header, based on the format, before the first event that matches the format is rendered.