Splunk Enterprise

Why are we receiving error from _internal index for Json logs?

Santosh2
Path Finder

We are receiving error from _internal index  for Json logs:

1. error: ERROR JsonLineBreaker - JSON StreamId:1254678906 had parsing error:Unexpected character: "s"

2. error: ERROR JsonLineBreaker - JSON StreamId:1254678906 had parsing error:Unexpected character: "a" 

sample logs:

{  [-]

       level: debug

      message: Creating a new instance of inquiry call

      timestamp: 2022-08-25T20:30:45.678Z

}

 

my props.conf:
TIME_PREFIX=timestamp" : "

TIME_FORMAT= %Y-%m-%dT%H:%M:%S.%3N

MAX_TIMESTAMP_LOOKAHEAD=40

TZ=UTC

how to resolve this issue.

Labels (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

I'm not sure about the exact cause of those messages, but it could be because the sample log is not valid JSON.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

I'm not sure about the exact cause of those messages, but it could be because the sample log is not valid JSON.

---
If this reply helps you, Karma would be appreciated.
0 Karma

Santosh2
Path Finder

but how can i identify that

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Among other things, proper JSON uses quotation marks around strings.

---
If this reply helps you, Karma would be appreciated.
0 Karma

Santosh2
Path Finder
 
Tags (1)
0 Karma
Get Updates on the Splunk Community!

Archived Metrics Now Available for APAC and EMEA realms

We’re excited to announce the launch of Archived Metrics in Splunk Infrastructure Monitoring for our customers ...

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Dashboard Challenge and Watch the .conf24 Global Broadcast!

The Splunk Community Dashboard Challenge is still happening, and it's not too late to enter for the week of ...