Getting Data In

Solution : event splitted even with SHOULD_LINEMERGE in props.conf

splunkreal
Motivator

Hello,
some events are not parsed correctly and not splitted only when there is timestamp especially with "slow" events.

 

0 Karma
1 Solution

splunkreal
Motivator

Solution applied from support KB https://splunk.my.site.com/customer/s/article/Multi-line-Breaking-Is-not-Working-after-Setting-up-th...

Indexers side
props.conf

[mysourcetype]
MAX_TIMESTAMP_LOOKAHEAD = 21
TIME_PREFIX = ^
TIME_FORMAT = %Y-%m-%d %H:%M:%S
SHOULD_LINEMERGE = true
NO_BINARY_CHECK = true

UF side
inputs.conf

# line merge
time_before_close = 60
multiline_event_extra_waittime = true

 

View solution in original post

0 Karma

splunkreal
Motivator

Solution applied from support KB https://splunk.my.site.com/customer/s/article/Multi-line-Breaking-Is-not-Working-after-Setting-up-th...

Indexers side
props.conf

[mysourcetype]
MAX_TIMESTAMP_LOOKAHEAD = 21
TIME_PREFIX = ^
TIME_FORMAT = %Y-%m-%d %H:%M:%S
SHOULD_LINEMERGE = true
NO_BINARY_CHECK = true

UF side
inputs.conf

# line merge
time_before_close = 60
multiline_event_extra_waittime = true

 

0 Karma
Get Updates on the Splunk Community!

Streamline Data Ingestion With Deployment Server Essentials

REGISTER NOW!Every day the list of sources Admins are responsible for gets bigger and bigger, often making the ...

Remediate Threats Faster and Simplify Investigations With Splunk Enterprise Security ...

REGISTER NOW!Join us for a Tech Talk around our latest release of Splunk Enterprise Security 7.2! We’ll walk ...

Introduction to Splunk AI

WATCH NOWHow are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. ...