Getting Data In

Safe TRUNCATE value on json events

andreibanaru
Explorer

What would be a “safe” value for the TRUNCATE option in props.conf?

I have some pretty big json events coming via HEC hitting the _json sourcetype (INDEXED_EXTRACTIONS=json).

Labels (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

"Safe" is a relative term.  To avoid all event truncations, the "safe" setting is TRUNCATE = 0, but that runs the risk of multiple events that are not line-broken correctly being ingested as a single event without warning.

Another "safe" approach is to set TRUNCATE to a reasonable value based on the expected event size plus a margin for error (maybe 10%).  If the logs indicate an event was truncated then investigate to see if the line-breaking settings should be changes or if the TRUNCATE setting should be increase.  Adjust and repeat.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Analytics Workspace deprecation

As of Splunk Cloud Platform 10.4.2604 and Splunk Enterprise 10.4, Analytics Workspace is now deprecated. ...

Splunk Developer Day Recap: Building, Publishing, and Growing on the Splunk Platform

Splunk Developer Day brought the Splunk developer community together for a practical look at what it means to ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...