Splunk Search

How to create a stats count by aggregating multiple fields?

dkotowsk
Engager

How do you create a stats count after aggregating multiple fields into one?

Example: Given the following table:

index saddr daddr
A 10.0.0.1 192.168.1.8
A 10.0.0.1 192.168.1.9

How can I get a table like the following?

index addr count
A 10.0.0.1 2
A 192.168.1.8 1
A 192.168.1.9 1
0 Karma
1 Solution

traxxasbreaker
Communicator

You can try something like this, though there may be a more efficient way to do it.

<Base Search> | eval addr=saddr+":"+daddr | makemv delim=":" addr | mvexpand addr | stats count by addr

Basically, you combine the source and destination addresses together and make that a multi-valued field, expand out those values so there's an event for each value, then use stats to group by those new values.

View solution in original post

traxxasbreaker
Communicator

You can try something like this, though there may be a more efficient way to do it.

<Base Search> | eval addr=saddr+":"+daddr | makemv delim=":" addr | mvexpand addr | stats count by addr

Basically, you combine the source and destination addresses together and make that a multi-valued field, expand out those values so there's an event for each value, then use stats to group by those new values.

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!

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...