topic Re: Log file monitoring, wrong parsing in Getting Data In

Log file monitoring, wrong parsing

faustf — Thu, 24 Aug 2017 09:58:43 GMT

Hy guys,
I've a nodejs application which is logging in a text file in JSON format using the winston library.

As you can see from the image, not all log lines are well parsed:

There are 2 logs line that are treated as one, and as a result, splunk is not able to detect the fields in the log lines (level, message ....)

This is my configuration:

[monitor:///home/user/myapp/log]
disabled = false
index = myindex
crcSalt = <SOURCE>
sourcetype = json

And this is my log file:

Re: Log file monitoring, wrong parsing

kmorris_splunk — Tue, 29 Sep 2020 15:25:54 GMT

I would recommend taking a sample of your data and brining it in through the GUI. When you do this, you can tweak the Breaking, Timestamping, etc... and see how it effects the way the data will be ingested. You can use the BREAK_ONLY_BEFORE parameter to apply a regex that identifies the beginning of each event.

Something like:

BREAK_ONLY_BEFORE       \{\"\w+\":

Once you get the linebreaking correct, save the sourcetype and then start feeding your data in through a forwarder.

Re: Log file monitoring, wrong parsing

s2_splunk — Thu, 24 Aug 2017 17:07:42 GMT

Share your sourcetype definition for "json" in props.conf, please.
If you intended to use the built-in sourcetype for json data, that would be "_json".

Re: Log file monitoring, wrong parsing

faustf — Fri, 25 Aug 2017 07:35:39 GMT

Thank you for your answer, but the problem was that the sourcetype was wrong: I wrote json instead o _json, as @ssievert wrote.

Re: Log file monitoring, wrong parsing

s2_splunk — Fri, 25 Aug 2017 15:50:37 GMT

Glad it works now. Please mark my answer as accepted for posterity. Thanks!