Getting Data In

Why the error while ingesting a JSON file "Jsonlinebreaker parsing error unexpected character /"?

New Member

I'm trying to ingest a json file and got the following error:

splunkd.log:01-07-2023 00:42:51.375 +0100 ERROR JsonLineBreaker [36024 parsing] - JSON StreamId:229865635822760533 had parsing error:Unexpected character: '/' - data_source="/opt/rfcanalyzer/var/log/housekeeping/dailyupdates.log", data_host="", data_sourcetype="_json"

Splunk complains about the following jsons:

{"tstamp": "2023-01-07 16:23:12", "severity": "INFO", "process": "", "message": "Removing rubbish from /ramtmp/20230107-splunk.txt"}
{"tstamp": "2023-01-07 16:28:43", "severity": "INFO", "process": "", "message": "Sorting /ramtmp/20230107-splunk.txt"}
{"tstamp": "2023-01-07 16:57:07", "severity": "INFO", "process": "", "message": "Converting all domains in /ramtmp/20230107-alldomains.txt to lowercase"}

{"tstamp": "2023-01-07 16:57:38", "severity": "INFO", "process": "", "message": "Sorting /ramtmp/20230107-alldomains.txt"}

According jsonlint these are valid jsons. I'm using the stand _json sourcetype.

Any idea what is wrong?




Labels (1)
Tags (1)
0 Karma
Get Updates on the Splunk Community!

March Community Office Hours Security Series Uncovered!

Hello Splunk Community! In March, Splunk Community Office Hours spotlighted our fabulous Splunk Threat ...

Stay Connected: Your Guide to April Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars in April. This post ...

Want to Reduce Costs, Mitigate Risk, Improve Performance, or Increase Efficiencies? ...

Splunk Lantern is Splunk’s customer success center that provides advice from Splunk experts on valuable data ...