Getting Data In

Filtering out servers

bgeshk
Engager

I'm trying to filter out servers that aren't getting a lot of traffic. So, I'm wondering how to filter out servers that are getting less than 10 requests per minute.

Right now, I'm getting the transactions per second of each JVM on all the servers:

index=att_prod_ecomm_open-api_rest sourcetype=att_openapi_access_log NOT "/openapi-rest-web/index.html" | bucket _time span=1s | stats count by _time | stats avg(count) as Average_TPS | appendcols [search index=att_prod_ecomm_open-api_rest sourcetype=att_openapi_access_log NOT "/openapi-rest-web/index.html" | stats count by source | stats count as jvm] | eval final = Average_TPS/jvm | gauge final

But i want to disregard the servers that get less than 10 requests per minute. Thanks!

Tags (2)
0 Karma

somesoni2
Revered Legend

Try like this

index=att_prod_ecomm_open-api_rest sourcetype=att_openapi_access_log NOT "/openapi-rest-web/index.html" | bucket _time span=1s | eval temp_time=_time | bucket span=1m temp_time | eventstats count by temp_time source | where count>=10| stats dc(source) as jvm count  by _time | eval avg=count/jvm | stats avg(avg) as Average_TPS| gauge Average_TPS

bgeshk
Engager

Thank you very much. That makes a lot more sense!

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...