Getting Data In

Why are events ingested using the journald modular input truncated at 4088 bytes?

chris_barrett
SplunkTrust
SplunkTrust

I'm pulling in events from the journal of a number of Linux hosts using the journald modular input.

I'm seeing truncated events every so often and, when I look at the length of _raw, I see that it's always 4088 bytes.

The man page for journalctl (https://www.freedesktop.org/software/systemd/man/journalctl.html) says that when events are outputted using JSON format, that "Fields larger than 4096 bytes are encoded as null values. (This may be turned off by passing --all, but be aware that this may allocate overly long JSON objects.)"

I'm presuming that that's what happening with the truncated events that I'm seeing.   Is anyone aware of a way around this?  I can't see any configuration setting associated with the journald modular input that would let me enable the '--all' flag.

FWIW, I'm running Splunk Enterprise 9.0.2

Labels (1)
Tags (2)
0 Karma
Get Updates on the Splunk Community!

Splunk MCP & Agentic AI: Machine Data Without Limits

  Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization ...

Finding Based Detections General Availability

Overview  We’ve come a long way, folks, but here in Enterprise Security 8.4 I’m happy to announce Finding ...

Get Your Hands Dirty (and Your Shoes Comfy): The Splunk Experience

Hands-On Learning and Technical Seminars  Sometimes, you just need to see the code. For those looking for a ...