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
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!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...