Splunk Search

Why does "mvexpand X" remove events with X=NULL?

macoo
Explorer

Why does mvexpand X remove events with X=NULL? As simple as that. It's illogical from my perspective, unless it's on purpose.

thank you!

Tags (1)

woodcock
Esteemed Legend

Either way of behaving makes some sense but, IMHO the way that it actually work makes more sense than the other.
Either way it could have worked, could easily be converted to the other.
In this case, just do this:

... | eval X = coalesce(X, "ImpossibleValueToDropLater")
| mvexpand X
| eval X = if(X="ImpossibleValueToDropLater", null(), X)

nick405060
Motivator

You're the best! Thanks. I decided to write less code but convert null values to strings, as posted in https://answers.splunk.com/answers/548304/mvexpand-gives-less-results.html:

eval username=coalesce(username,"") | mvexpand username
0 Karma

woodcock
Esteemed Legend

If this worked for you, click "Accept" to close the question.

0 Karma
Get Updates on the Splunk Community!

Splunk Search APIを使えば調査過程が残せます

   このゲストブログは、JCOM株式会社の情報セキュリティ本部・専任部長である渡辺慎太郎氏によって執筆されました。 Note: This article is published in both Japanese ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...