Getting Data In

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

Cyb0rg42
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="vrfcanalyzer.rfcanalyzer.net", data_sourcetype="_json"

Splunk complains about the following jsons:

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

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

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

Any idea what is wrong?

Cheers,

Karl

 

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

Splunk Mobile: Your Brand-New Home Screen

Meet Your New Mobile Hub  Hello Splunk Community!  Staying connected to your data—no matter where you are—is ...

Introducing Value Insights (Beta): Understand the Business Impact your organization ...

Real progress on your strategic priorities starts with knowing the business outcomes your teams are delivering ...

Enterprise Security (ES) Essentials 8.3 is Now GA — Smarter Detections, Faster ...

As of today, Enterprise Security (ES) Essentials 8.3 is now generally available, helping SOC teams simplify ...