Splunk Search

Why when I use mvzip , mvexpand, mvindex(split, the first 4 fields keep repeating?

karu0711
Communicator

 

index="main" sourcetype="vrea"
| eval nested_payload=mvzip(info, solution, "---")
| mvexpand nested_payload
| eval info=mvindex(split(nested_payload, "---"), 1)
| eval solution=mvindex(split(nested_payload, "---"), 0)
| eval nested_payload=mvzip(line, more, "---")
| mvexpand nested_payload
| eval line=mvindex(split(nested_payload, "---"), 1)
| eval more=mvindex(split(nested_payload, "---"), 0)
| eval nested_payload=mvzip(ID, Severity, "---")
| mvexpand nested_payload
| eval Severity=mvindex(split(nested_payload, "---"), 1)
| eval CWE_ID=mvindex(split(nested_payload, "---"), 0)
| table info solution ID Severity line more

 

 

when use the SPL my table fields value first 4 fields keep repeating same value but last 2 field "line and more" correct value? 

anyone know why it is happening?

Labels (1)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

It sounds like mvexpand is doing exactly what it is supposed to do, that is, create duplicate events except for the field being expanded, which will contain each of the values in the multi-value field in separate events.

0 Karma

yuanliu
SplunkTrust
SplunkTrust

Please explain the question with sample data and sample output, then explain why you feel the output is wrong.  Otherwise it's just a waste of time for others to try to speculate what the question really is.

0 Karma
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...