Getting Data In

props.conf config for line breaking

ssaenger
Communicator

Hi All,

I am having problems splitting lines of a log file.
the log entry is below;

[DEBUG 2019-09-26 09:15:57:765] Logger Proxy STARTED
[DEBUG 2019-09-26 09:15:57:765] Logger Servlet Called (13024624) times
[DEBUG 2019-09-26 09:15:57:765] Logger SetResponseDefaults
[FATAL 2019-09-26 09:15:57:765] Logger Proxy - Illegal or missing SubscriberId

below is my props.conf file entry

[jams_log]
SHOULD_LINEMERGE = true
BREAK_ONLY_BEFORE_DATE = false
BREAK_ONLY_BEFORE = ^[\D{5}\s\d{4}-\d{2}-\d{2}\s\d{2}:\d{2}:\d{2}.\d{3}]
MAX_TIMESTAMP_LOOKAHEAD = 31
TIME_PREFIX = ^

I thought it was because i did not have TIME_FORMAT, however this did not work either.

any help would be much appreciated.

0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi ssaenger,
at first I suggest to test your props.conf using the guided web interface.
Than, did you tried SHOULD_LINEMERGE=false?
Then I see that the TIME_PREFIX isn't correct, so try something like this:

[jams_log]
SHOULD_LINEMERGE = true
LINE_BREAKER = \[\w+\s+\d{4}-\d{2}-\d{2}\s+\d{2}:\d{2}:\d{2}.\d{3}\]
MAX_TIMESTAMP_LOOKAHEAD = 29
TIME_PREFIX = ^\[\w+\s+

Bye.
Giuseppe

View solution in original post

gcusello
SplunkTrust
SplunkTrust

Hi ssaenger,
at first I suggest to test your props.conf using the guided web interface.
Than, did you tried SHOULD_LINEMERGE=false?
Then I see that the TIME_PREFIX isn't correct, so try something like this:

[jams_log]
SHOULD_LINEMERGE = true
LINE_BREAKER = \[\w+\s+\d{4}-\d{2}-\d{2}\s+\d{2}:\d{2}:\d{2}.\d{3}\]
MAX_TIMESTAMP_LOOKAHEAD = 29
TIME_PREFIX = ^\[\w+\s+

Bye.
Giuseppe

ssaenger
Communicator

Thank you Giuseppe,

Yes, from looking at your answer I understand my mistake - slowly learning 🙂

thanks,
Steve

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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...