Skip to main content
Solved

Hello Im Having Issues With Json Unroll And I'm Not Sure Why It's Not Working. I've Tried Everything Imaginable Path…

  • May 15, 2026
  • 4 replies
  • 4 views

This message originated from Cribl Community Slack.
Click here to view the original link.

hello im having issues with JSON Unroll and I'm not sure why it's not working. I've tried everything imaginable path with quotes, without quotes, etc. but it still does not work. total.in_bytes is the name of the array every element of which should be extracted to a field test as a new event. But it is not working

Links for this message:
image.png

Best answer by Jon Rust

2 issues. 1. Unroll is likely what you want, not JSON unroll. I'm not clear on the history behind the distinction, but JSON Unroll is intended for stringified JSON inside _raw i think. 2. You're going to have some pain from the dot in the field name. You can use the __e[] notation to get around it

Links for this message:
image.png

4 replies

Jon Rust
Forum|alt.badge.img
  • Employee
  • Answer
  • May 15, 2026
2 issues. 1. Unroll is likely what you want, not JSON unroll. I'm not clear on the history behind the distinction, but JSON Unroll is intended for stringified JSON inside _raw i think. 2. You're going to have some pain from the dot in the field name. You can use the __e[] notation to get around it

Links for this message:
image.png

Jon Rust
Forum|alt.badge.img
  • Employee
  • May 15, 2026
I always recommend the destination field match the source field. Otherwise you'll end of with a copy of the original field in all the unrolled events. COuld blow up memory and processing usage.

Jon Rust
Forum|alt.badge.img
  • Employee
  • May 15, 2026
Rough guidance: Use Unroll for generic arrays, and JSON Unroll when the payload is a JSON string in _raw (that contains an array)

  • Employee
  • May 15, 2026
+1 to all Jon said. You also might find the "Advanced Mode" button useful to more quickly examine what you're extracting

Links for this message:
Screenshot 2026-05-13 at 10.49.05 AM.png
Screenshot 2026-05-13 at 10.49.31 AM.png
Screenshot 2026-05-13 at 10.49.46 AM.png