Skip to content

docs: pipeline: parsers: json: document nesting depth limit #2732

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: parsers: json: document nesting depth limit #2732

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
8 changes: 8 additions & 0 deletions pipeline/parsers/json.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,3 +44,11 @@ After processing, its internal representation will be:
```

The time was converted to a UTC timestamp and the map was reduced to each component of the original message.

## Nesting depth limit

In Fluent Bit version 5.1.3 and greater, this parser accepts at most 32 levels of nested objects and arrays. The outermost object counts as the first level.

A log entry nested deeper than this limit fails to parse. Fluent Bit doesn't log a message that identifies the nesting depth as the cause, so a record that's rejected for this reason looks the same as a record rejected for malformed JSON. If records that appear to be valid JSON are being dropped, check how deeply they nest.

Because the limit applies while the JSON is converted to the internal binary representation, it applies to the whole log entry, not to individual keys.
Loading