Splunk Search

Group results by common value

dcarriger
Engager

Alright. My current query looks something like this:

sourcetype=email action=accept ip=127.0.0.1 | stats count(subject), dc(recipients) by ip, subject

And this produces output like the following:

ip subject count dc(recipients)

127.0.0.1 email1 10 10

127.0.0.1 email2 5 2

127.0.0.1 email3 1 1

How would I query this instead so I can group those results together by IP so I'd be looking at a format like this?

ip subject count dc(recipients)

127.0.0.1 email1 10 10

email2 5 2

email3 1 1

I haven't figured out a query yet that will let me group by IP while still getting a count for each subject value, and a distinct count for the number of recipients for each subject value.

Tags (1)
0 Karma
1 Solution

somesoni2
Revered Legend

Try this,

sourcetype=email action=accept ip=127.0.0.1 | stats count(subject) as count, dc(recipients) as recipients by ip, subject | stats list(subject) as subject , list(count) as count, list(recipients) as recipients by ip

View solution in original post

somesoni2
Revered Legend

Try this,

sourcetype=email action=accept ip=127.0.0.1 | stats count(subject) as count, dc(recipients) as recipients by ip, subject | stats list(subject) as subject , list(count) as count, list(recipients) as recipients by ip

bbsoc1
Engager

Beautiful solution. Thanks for providing. Found this independently 2 yrs after you posted it.

0 Karma

dcarriger
Engager

Awesome! This does exactly what I need it to. Thanks!

0 Karma
Get Updates on the Splunk Community!

Shape the Future of Splunk: Join the Product Research Lab!

Join the Splunk Product Research Lab and connect with us in the Slack channel #product-research-lab to get ...

Auto-Injector for Everything Else: Making OpenTelemetry Truly Universal

You might have seen Splunk’s recent announcement about donating the OpenTelemetry Injector to the ...

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...