Splunk Search

sum(count) returning 0 events

pedropiin
Path Finder

Hi everyone.

I have a query that basically filters certain events and sums them by category. But I'm facing issues when dealing with stats sum.

The query is of the form

 

index=main source=...
...
...
| stats count BY name, ticket
| stats sum(count) as numOfTickets by name

 

 

Using some test data, removing the last line gives me a table with only one row of the form:
" name    | tickets               | count "
" name1 | ticket_name1 | 1"
(considering the first line as the names of the fields).
Whenever I run the last line, that is, "stats sum(count)..." , it returns 0 events. 

I've already tried to, for example, redundantly check that count is a numeric value by doing "eval count = tonumber(count)".

Why is this happening?

Thank you in advance

Labels (1)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Your sample test data shows a field called "tickets" when your stats command is using a field called "ticket" - is it simply a typo in your example, or in your actual search?

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @pedropiin ,

this search hasn't sense, you could run:

index=main source=...
...
...
| stats count BY name

Ciao.

Giuseppe

0 Karma

pedropiin
Path Finder

Hi Giuseppe. Thank you for your response.

This is just with test data. When I deal with a real scenario, face the same issue but it I can't simply run "count".

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @pedropiin ,

there isn't any reason for your behavior: after a stats command you have only the fields present in the command.

Could you share the full search?

Ciao.

Giuseppe

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!

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 ...