Lua

Lua Filter allows you to modify the incoming records using custom Lua Scripts.

Due to the necessity to have a flexible filtering mechanism, now is possible to extend Fluent Bit capabilities writing simple filters using Lua programming language. A Lua based filter takes two steps:

Configuration Parameters

Lua function name that will be triggered to do filtering. It's assumed that the function is declared inside the Script defined above.

Type_int_key

If the key is matched, that field will be converted to integer.

Getting Started

In order to test the filter, you can run the plugin from the command line or through the configuration file. The following examples uses the dummy input plugin for data ingestion, invoke Lua filter using the test.lua script and calls the cb_print() function which only print the same information to the standard output:

Command Line

Configuration File

In your main configuration file append the following Input, Filter & Output sections:

[INPUT]

Name dummy

​

[FILTER]

Name lua

Match *

script test.lua

call cb_print

​

[OUTPUT]

Name null

Match *

Lua Script Filter API

The life cycle of a filter have the following steps:

Upon Tag matching by filter_lua, it may process or bypass the record.

If filter_lua accepts the record, it will invoke the function defined in the call property which basically is the name of a function defined in the Lua script.

Invoke Lua function passing each record in JSON format.

Upon return, validate return value and take some action (described above)

Callback Prototype

The Lua script can have one or multiple callbacks that can be used by filter_lua, it prototype is as follows:

functioncb_print(tag, timestamp, record)

return code, timestamp, record

end

Function Arguments

name

description

tag

Name of the tag associated with the incoming record.

timestamp

Unix timestamp with nanoseconds associated with the incoming record. The original format is a double (seconds.nanoseconds)

record

Lua table with the record content

Return Values

Each callback must return three values:

name

data type

description

code

integer

The code return value represents the result and further action that may follows. If code equals -1, means that filter_lua must drop the record. If code equals 0 the record will not be modified, otherwise if code equals 1, means the original timestamp or record have been modified so it must be replaced by the returned values from timestamp (second return value) and record (third return value).

timestamp

double

If code equals 1, the original record timestamp will be replaced with this new value.

record

table

if code equals 1, the original record information will be replaced with this new value. Note that the format of this value must be a valid Lua table.

Code Examples

For functional examples of this interface, please refer to the code samples provided in the source code of the project located here: