Getting Data In

Split not working

amitg_23
New Member

I have following data after this query:

index=sdlocp_epo-solutiontest sourcetype="kube:container:customer-soap-app"
| spath
| search level="SERVICE_PERF"
| table message

|2800|BackOffice|T999999||Servcie1|8b81dbd0-ba0f-11e9-8912-914decccd432|Success|67|NA|NA|NA
|2800|BackOffice|T999999||Servcie1|8b81dbd0-ba0f-11e9-8912-914decccd432|Success|67|NA|NA|NA
|2800|BackOffice|T999999||Servcie1|8b81dbd0-ba0f-11e9-8912-914decccd432|Success|67|NA|NA|NA
|2800|BackOffice|T999999||Servcie2|8b81dbd0-ba0f-11e9-8912-914decccd432|Success|16|NA|NA|NA
|2800|BackOffice|T999999||Servcie2|8b81dbd0-ba0f-11e9-8912-914decccd432|Success|16|NA|NA|NA
|2800|BackOffice|T999999||Servcie2|8b81dbd0-ba0f-11e9-8912-914decccd432|Success|16|NA|NA|NA

I then run the following query:

index=sdlocp_epo-solutiontest sourcetype="kube:container:customer-soap-app"
| spath
| search level="NG_SERVICE_PERFORMANCE"
| table message
| eval fields=split(message,"|") , etime=mvindex(fields,8)
| table etime

It fails.

When I run it with _raw instead of message in split, it works. Why is that so?

I am using logs in JSON format.

Thanks in advance.

Tags (2)
0 Karma

amitg_23
New Member

Sorry, second query is:
index=sdlocp_epo-solutiontest sourcetype="kube:container:customer-soap-app"
| spath
| search level="SERVICE_PERF"
| table message
| eval fields=split(message,"|") , etime=mvindex(fields,8)
| table etime

0 Karma

mayurr98
Super Champion

I am not sure why its not working because the syntax looks perfect. Do you get any error?

Well you could use rex to get the desired result.

index=sdlocp_epo-solutiontest sourcetype="kube:container:customer-soap-app"
| spath 
| search level="SERVICE_PERF" 
| table message 
| rex field=message "\|\w+\|(?<etime>\d+)\|"
| table etime

let me know if this helps!

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

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...