Event Streams

Page Layout

Event streams are configured from this page. For each device integration/feed, Fluency will treat it as a logical “event stream”.

Each event stream should be associated with a correct parser. Since Event processing is done on the server side, this configuration only needs to be done once, on the server, per each different event type.

Refer to the Event Processing page under the Device Integration section of this document for more details and examples.

The first section of this page contains three tables with event stream processing rules. The first table contains inputs to be processed. The user can apply filters and lambdas to event streams, selecting events based on source, sender, tags, and/or group. These filters and lambdas allow the user to configure and parse data for display on the Global -> Events page.

Event Stream Lambdas are located in the last table on the Event Streams page.

Adding an Input Stream

A new input stream can be defined by clicking the “+ NEW RULE” button. Clicking this will open a wizard to guide you through the process.

First, name the input stream and select its location: input to be processed, data to be discarded, or data saved to the database.

Next, there is an option to choose the sink for the data. This determines if the data will be discarded (ends here), saved (moves on), or n/a (undecided).

The next step allows you to choose which field(s) to match based on source, sender, tags, and/or group. Clicking the “Match All” slider at the top causes any filters or lambdas selected to apply to every event.

After this, the user is able to add filters. These filters are predefined and can be used for parsing, formatting, or data normalization.

The last step is to add lambdas. These can be written by the user to parse data that does not have a filter preconfigured.

Adding a Lambda Script

To create a new lambda script, click the “+ NEW LAMBDA” button in the bottom right corner of the table.

Lambda scripts can be used to parse events that do not already have parsers configured. They can also be used to create flows using the data present in an event’s fields. They can be written in javascript or groovy.

At the top of the page, enter a name and description for the lambda script. After saving the script, the name cannot be changed.

Use the “Script” tab to write the script. The “Input” tab allows a sample input to be entered; it can be used for testing. The console logs with display any errors or print statements. The output will display the output data after parsing.