Getting Data In

JSON input: How can I split these values for each line break a new row is generated?

wes7bb
New Member

alt text

Hi there,
I have a JSON input in Splunk and Splunk extracts the data. But it is not generating for each application in my case WCMS or ESIWEB as their own entry that is possible to sort through this data. All this information is related to one event.

How can I split these values?
I want that for each line break a new row is generated.

Thanks a lot in advance!

Yours
Sina

Tags (2)
0 Karma
1 Solution

kamlesh_vaghela
SplunkTrust
SplunkTrust

@wes7bb ,

Can you please try this?

YOUR_SEARCH
| rename 'data{}.application.name' as 'application_name', 'data{}.package.name' as 'package_name', 'data{}.planned_from' as 'planned_from'
| eval tempField= mvzip(mvzip(application_name,package_name),planned_from) 
| stats count by tempField
| eval application_name = mvindex(split(tempField,","),0), package_name= mvindex(split(tempField,","),1), planned_from=mvindex(split(tempField,","),2) 
| table application_name package_name planned_from

Thanks

View solution in original post

0 Karma

kamlesh_vaghela
SplunkTrust
SplunkTrust

@wes7bb ,

Can you please try this?

YOUR_SEARCH
| rename 'data{}.application.name' as 'application_name', 'data{}.package.name' as 'package_name', 'data{}.planned_from' as 'planned_from'
| eval tempField= mvzip(mvzip(application_name,package_name),planned_from) 
| stats count by tempField
| eval application_name = mvindex(split(tempField,","),0), package_name= mvindex(split(tempField,","),1), planned_from=mvindex(split(tempField,","),2) 
| table application_name package_name planned_from

Thanks

0 Karma

wes7bb
New Member

Thanks a lot for your help! It works!

0 Karma
Get Updates on the Splunk Community!

Aligning Observability Costs with Business Value: Practical Strategies

 Join us for an engaging Tech Talk on Aligning Observability Costs with Business Value: Practical ...

Mastering Data Pipelines: Unlocking Value with Splunk

 In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...