Splunk Search

Query help with search using sum(count) and 2 subsearches using count

subtrakt
Contributor

I have a query that combines 1 search and 2 sub-searches. The main search is a summary index and sum(count) in the timechart to look right. The 2 sub searches do not need sum(count) - they just need "count" so they are represented properly on the timechart.

I was thinking if there was a way to convert sum(count) to count I would be good.

This summary index runs every 15 minutes and buckets by the minute:

Here's my Attempt to translate sum(count) to count:
index="summary_onemin" error | evenstats sum(count) as count by _time | append [| search index=power_user "null" | bucket _time span=2m | eval CODE=powerNULL] | timechart span=2m by CODE

Without the subsearch the search would look like this and works as intended:
index="summary_onemin" error | timechart sum(count) as COUNT by CODE

1 Solution

somesoni2
Revered Legend

Try this

 index="summary_onemin" error | table _time CODE count 
| append [search index=power_user "null" | bucket _time span=2m | eval CODE=powerNULL
| stats count by _time, CODE] 
| timechart span=2m sum(count) as count by CODE

View solution in original post

somesoni2
Revered Legend

Try this

 index="summary_onemin" error | table _time CODE count 
| append [search index=power_user "null" | bucket _time span=2m | eval CODE=powerNULL
| stats count by _time, CODE] 
| timechart span=2m sum(count) as count by CODE

subtrakt
Contributor

Thanks Somesoni!

0 Karma

somesoni2
Revered Legend

Can you post your full search?

0 Karma
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!

Best Practices: Splunk auto adjust pipeline queue

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

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

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