Getting Data In

JSON/Syslog and SPATH

matthewparry
Path Finder

Hi,

I have JSON data being indexed from a syslog file i.e

Nov  2 23:04:47 host1 /usr/local/bin/audit.rb[24503]: { "@fields" : {  "action" : "check", "agent" : "server", "caller" : "user", "callerhost" : "system", "data" : "{:process_results=>true}", "request_time" : 1351746758, "uniqid" : "73670e799fbf576b9225278cc46709c0" }, "@message" : "message", "@source" : "audit", "@source_host" : "host", "@tags" : [  ], "@timestamp" : "2012-11-01T05:12:38.169418Z", "@type" : "audit" }

The problem is I cannot use spath to extract fields, i.e

 | spath output=action [email protected]

If I remove the syslog section and only index the JSON data then it works without problems, i.e if the data is just.

{ "@fields" : {  "action" : "check", "agent" : "server", "caller" : "user", "callerhost" : "system", "data" : "{:process_results=>true}", "request_time" : 1351746758, "uniqid" : "73670e799fbf576b9225278cc46709c0" }, "@message" : "message", "@source" : "audit", "@source_host" : "host", "@tags" : [  ], "@timestamp" : "2012-11-01T05:12:38.169418Z", "@type" : "audit" }

Is this normal behaviour, is there a way around it whilst still being able to use the spath function?

Thanks.

Tags (3)
0 Karma
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

this is normal. spath operates on either XML or JSON, and with the extra info, your data is not JSON. You can simply use eval prior to using spath to strip out the syslog info prior to piping to spath.

View solution in original post

0 Karma

gkanapathy
Splunk Employee
Splunk Employee

this is normal. spath operates on either XML or JSON, and with the extra info, your data is not JSON. You can simply use eval prior to using spath to strip out the syslog info prior to piping to spath.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...