Splunk Search

DBConnect Events Truncate Despite props.conf

graememeyer
Explorer

It seems that DBConnect inputs does no respect the props.conf configuration for event truncation.

Example props:

[epo]
LINE_BREAKER_LOOKBEHIND = 100000
TRUNCATE = 0
MAX_EVENTS = 100000

(Applied in System + Local).

/answers/225697 has a reply suggesting to use [source::...tpl_*.dbmonevt], but I am unsure what this is and a child reply suggests that this isn't effective either.

Does anyone know of a way to get DBConnect to stop truncating the events?

1 Solution

graememeyer
Explorer

Copying my solution here in case anyone else needs it:

Set TRUNCATE=0 in the following locations:

/opt/splunk_hf/etc/apps/dbx/default

[source::...kv_*.dbmonevt]
SHOULD_LINEMERGE = false
HEADER_MODE = firstline
LINE_BREAKER = ([\r\n]+)
priority = 101
TRUNCATE=0


/opt/splunk_hf/etc/apps/dbx/local

[sourcetype]
LINE_BREAKER_LOOKBEHIND = 100000
TRUNCATE = 0
MAX_EVENTS = 100000


/opt/splunk_hf/etc/system/local

[sourcetype]
TRUNCATE = 0

Replace "sourcetype" with whatever your sourcetype is called (mine was "epo")

View solution in original post

graememeyer
Explorer

Copying my solution here in case anyone else needs it:

Set TRUNCATE=0 in the following locations:

/opt/splunk_hf/etc/apps/dbx/default

[source::...kv_*.dbmonevt]
SHOULD_LINEMERGE = false
HEADER_MODE = firstline
LINE_BREAKER = ([\r\n]+)
priority = 101
TRUNCATE=0


/opt/splunk_hf/etc/apps/dbx/local

[sourcetype]
LINE_BREAKER_LOOKBEHIND = 100000
TRUNCATE = 0
MAX_EVENTS = 100000


/opt/splunk_hf/etc/system/local

[sourcetype]
TRUNCATE = 0

Replace "sourcetype" with whatever your sourcetype is called (mine was "epo")

cpetterborg
SplunkTrust
SplunkTrust

How are the event getting truncated? Are you losing columns, or are you losing data from the middle of a column? How many characters are you getting in each event? Etc.

Is epo the sourcetype?

0 Karma

graememeyer
Explorer

EPO is the sourcetype, events are being truncated at 10K characters and it's cutting off in the middle of a column, but not printing the remaining columns afterwards.

0 Karma

cpetterborg
SplunkTrust
SplunkTrust
0 Karma

graememeyer
Explorer

Thanks cpetterborg but I solved the issue. Seems there's another props file in /opt/splunk_hf/etc/apps/dbx/default and you have to set TRUNCATE=0 in the [source::...kv_*.dbmonevt] sourcetype as well.

So for anyone coming in from Google, I have set TRUNCATE=0 in the following locations:

/opt/splunk_hf/etc/apps/dbx/default

[source::...kv_*.dbmonevt]
SHOULD_LINEMERGE = false
HEADER_MODE = firstline
LINE_BREAKER = ([\r\n]+)
priority = 101
TRUNCATE=0


/opt/splunk_hf/etc/apps/dbx/local

[sourcetype]
LINE_BREAKER_LOOKBEHIND = 100000
TRUNCATE = 0
MAX_EVENTS = 100000


/opt/splunk_hf/etc/system/local

[sourcetype]
TRUNCATE = 0

And that's done the trick 🙂

Replace "sourcetype" with whatever your sourcetype is called (mine was "epo")

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...