Splunk Search

How to limit the aggregate value like 'having' in sql

arunbs
Explorer

Hi, I want to filter the records after aggrigating it, almost similar to 'having' in sql. Here is search query:

source="rest://Data" 
| eval limit = substr(CreationDate, 1,4) | where limit = 2013 
| where 
(projectName=="Proj-1")  OR  
| chart 
dc(eval(case(State=="QA",ObjectID))) as "QA", 
dc(eval(case(State=="Dev",ObjectID))) as "Dev"
by Owner

Here, i want to show only those owners who have a non-zero QA count.

Thanks in advance.
Arun.

Tags (2)
0 Karma
1 Solution

kristian_kolb
Ultra Champion

I'm not quite sure I follow what you want to achieve. You can probably do this more efficiently;

The following would be a good start, but there was a missing statement after the 'OR' in your search:

source="rest://data" CreationDate=2013* State = QA OR State = Dev projectName=Proj-1 OR <something else> | chart dc(ObjectID) by State, Owner

Hope this helps,

K

View solution in original post

arunbs
Explorer

Thanks kristian and daniels for the quick answers. It indeed helps us to get what we wanted and also optimized it.

0 Karma

sdaniels
Splunk Employee
Splunk Employee

Take a look at this. Gives a nice comparison and a Splunk example to match the SQL.

http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/SQLtoSplunk

kristian_kolb
Ultra Champion

I'm not quite sure I follow what you want to achieve. You can probably do this more efficiently;

The following would be a good start, but there was a missing statement after the 'OR' in your search:

source="rest://data" CreationDate=2013* State = QA OR State = Dev projectName=Proj-1 OR <something else> | chart dc(ObjectID) by State, Owner

Hope this helps,

K

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...