Splunk Search

Modifying stats count to include fields with zero-values

HallGM
Engager

I have some data with a field called "priority", which has a value from P1 -> P5.

this search query:

...
| stats count as Quantity by priority

 

produces a table that looks something like this:

priorityQuantity
P21
P31
P46
P53

 

As you can see,  there are no data entries with a priority of "P1". However, I would like to actually include that as a row in the table and show that there is a quantity of "0". Ideally I would want to include all 5 priority levels for any dataset, even when they are empty

Can anyone help and let me know how I can do this? Is there a way to specify which values to count?

Labels (1)
0 Karma
1 Solution

johnhuang
Motivator

 

...
| eval count=1
| append [| makeresults | eval priority=SPLIT("P1,P2,P3,P4,P5", ",") | mvexpand priority | eval count=0]
| stats sum(count) AS Quantity BY priority

 

View solution in original post

VatsalJagani
SplunkTrust
SplunkTrust

Use below:

| append [| makeresults | eval priority=split("P1,P2,P3,P4,P5", ",") | mvexpand priority | eval count=0]
| stats sum(count) AS Quantity BY priority
0 Karma

johnhuang
Motivator

 

...
| eval count=1
| append [| makeresults | eval priority=SPLIT("P1,P2,P3,P4,P5", ",") | mvexpand priority | eval count=0]
| stats sum(count) AS Quantity BY priority

 

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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...