Skip to content

docs: pipeline: inputs: tcp: document unprocessable JSON payload handling #2757

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
eschabell merged 1 commit into from
Oct 9, 2026
Merged

docs: pipeline: inputs: tcp: document unprocessable JSON payload handling #2757

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 2 additions & 0 deletions pipeline/inputs/tcp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ The plugin supports the following configuration parameters:
| `threaded` | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). | `false` |
| `workers` | The number of listener workers that accept and process incoming connections on the port. | `1` |

In v5.1.3 or later, when `format` is `json` and a payload can't be encoded or ingested, the plugin logs the warning `skipping unprocessable JSON payload` and consumes the affected bytes instead of processing them again. Any records from that payload that were already routed before the failure remain delivered; consuming the bytes prevents them from being duplicated on a later read.

## Get started

To receive JSON messages over TCP, you can run the plugin from the command line or through the configuration file.
Expand Down
Loading