Skip to content

Add delimiter parameter of in_tcp #640

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kenhys merged 2 commits into from
Jul 24, 2026
Merged

Add delimiter parameter of in_tcp #640

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c4701bc
Add delimiter parameter of in_tcp
Watson1978 Jul 23, 2026
b392028
Add comment in example
Watson1978 Jul 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 23 additions & 1 deletion input/tcp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,6 +141,29 @@ You will get something like below:

The maximum number of bytes for the message.

### `delimiter`

| type | default | version |
| :--- | :--- | :--- |
| string | `"\n"` \(newline\) | 0.10.51 |

The payload is read up to this character. Since a TCP stream has no message boundary, `in_tcp` splits the received bytes at every occurrence of this string and passes each part to the `<parse>` section. The delimiter itself is not included in the parsed message.

This is not a pattern but a plain string, so a delimiter of two or more characters can also be specified:

```text
<source>
@type tcp
tag tcp.events
delimiter "||" # It will work expectedly if it splits with '||' against incoming "foo||bar", not work for 'foo|bar'.
<parse>
@type json
</parse>
</source>
```

When `message_length_limit` is set and the data received before the next delimiter exceeds that limit, the buffer is cleared and the remaining bytes are discarded until the next delimiter arrives. The subsequent messages are processed as usual.

### `<transport>` Section

| type | default | available values | version |
Expand Down Expand Up @@ -313,4 +336,3 @@ $ openssl s_client -connect localhost:20001 \
If the connection gets established successfully, your setup is working fine.

If this article is incorrect or outdated, or omits critical information, please [let us know](https://github.com/fluent/fluentd-docs-gitbook/issues?state=open). [Fluentd](http://www.fluentd.org/) is an open-source project under [Cloud Native Computing Foundation \(CNCF\)](https://cncf.io/). All components are available under the Apache 2 License.