TCP
The tcp input plugin allows to retrieve structured JSON or raw messages over a TCP network interface (TCP port).

Configuration Parameters

The plugin supports the following configuration parameters:
Key
Description
Default
Listen
Listener network interface.
0.0.0.0
Port
TCP port where listening for connections
5170
Buffer_Size
Specify the maximum buffer size in KB to receive a JSON message. If not set, the default size will be the value of Chunk_Size.
Chunk_Size
By default the buffer to store the incoming JSON messages, do not allocate the maximum memory allowed, instead it allocate memory when is required. The rounds of allocations are set by Chunk_Size in KB. If not set, Chunk_Size is equal to 32 (32KB).
32
Format
Specify the expected payload format. It support the options json and none. When using json, it expects JSON maps, when is set to none, it will split every record using the defined Separator (option below).
json
Separator
When the expected Format is set to none, Fluent Bit needs a separator string to split the records. By default it uses the breakline character \n (LF or 0x10).
\n

Getting Started

In order to receive JSON messages over TCP, you can run the plugin from the command line or through the configuration file:

Command Line

From the command line you can let Fluent Bit listen for JSON messages with the following options:
1
$ fluent-bit -i tcp -o stdout
Copied!
By default the service will listen an all interfaces (0.0.0.0) through TCP port 5170, optionally you can change this directly, e.g:
1
$ fluent-bit -i tcp://192.168.3.2:9090 -o stdout
Copied!
In the example the JSON messages will only arrive through network interface under 192.168.3.2 address and TCP Port 9090.

Configuration File

In your main configuration file append the following Input & Output sections:
1
[INPUT]
2
Name tcp
3
Listen 0.0.0.0
4
Port 5170
5
Chunk_Size 32
6
Buffer_Size 64
7
Format json
8
9
[OUTPUT]
10
Name stdout
11
Match *
Copied!

Testing

Once Fluent Bit is running, you can send some messages using the netcat:
1
$ echo '{"key 1": 123456789, "key 2": "abcdefg"}' | nc 127.0.0.1 5170
Copied!
In Fluent Bit we should see the following output:
1
$ bin/fluent-bit -i tcp -o stdout -f 1
2
Fluent Bit v1.x.x
3
* Copyright (C) 2019-2020 The Fluent Bit Authors
4
* Copyright (C) 2015-2018 Treasure Data
5
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
6
* https://fluentbit.io
7
8
[2019/10/03 09:19:34] [ info] [storage] initializing...
9
[2019/10/03 09:19:34] [ info] [storage] in-memory
10
[2019/10/03 09:19:34] [ info] [engine] started (pid=14569)
11
[2019/10/03 09:19:34] [ info] [in_tcp] binding 0.0.0.0:5170
12
[2019/10/03 09:19:34] [ info] [sp] stream processor started
13
[0] tcp.0: [1570115975.581246030, {"key 1"=>123456789, "key 2"=>"abcdefg"}]
Copied!

Performance Considerations

When receiving payloads in JSON format, there are high performance penalties. Parsing JSON is a very expensive task so you could expect your CPU usage increase under high load environments.
To get faster data ingestion, consider to use the option Format none to avoid JSON parsing if not needed.
Last modified 1yr ago