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
Get Updates on the Splunk Community!

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...

Detecting Remote Code Executions With the Splunk Threat Research Team

REGISTER NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If ...