Knowledge Management

Using per_second with summary index not working

techols
New Member

I have a saved search:

source=/opt/app/workload/MCRRepo/*/*.csv
| rex "(?.*),(?.*),(?.*),(?.*),(?.*),(?.*)"
| search componentName=ServiceComponent* measurementName=transactionAttempts
| sitimechart span=5m per_second(counterValue)

When I run the normal version of this query over a 24 hour period:

source=/opt/app/workload/MCRRepo/*/*.csv
| rex "(?.*),(?.*),(?.*),(?.*),(?.*),(?.*)"
| search componentName=ServiceComponent* measurementName=transactionAttempts
| timechart span=5m per_second(counterValue)

I get per_second ranges of up to 7000 TPS which matches the expected range of my data. But when I run the query against the summary index using the query over a 7 day or longer period:

index=summary search_name="MCR_TPS" 
| timechart span=5min per_second(counterValue)

I get per_second ranges up to 200K. What am I missing? The TPS should still range up to 7000 TPS for each of the 7 days.

0 Karma

woodcock
Esteemed Legend

What is the timepicker window for the populating search that is dropping events into your summary index?

0 Karma

DalJeanis
SplunkTrust
SplunkTrust

try this

index=summary search_name="MCR_TPS"

and this

index=summary search_name="MCR_TPS" | sitimechart span=5min per_second(counterValue)
0 Karma
Get Updates on the Splunk Community!

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...