Splunk Search

Optimizing metrics based searches?

auzelevski
Explorer

Hello,

I have the following query in one of the panels in my dashboard.

 

 

 

| mstats p95(prometheus.container_memory_working_set_bytes) as p95_memory_bytes span=1m where pod=sf-mcdata--hydration-worker* AND stack=$stackLower$ by stack
| stats min(p95_memory_bytes) as min_p95_memory_bytes by _time
| timechart span=1m count as Availability
| eval Span=1
              | stats sum(Availability) as totalAvailability, sum(Span) as totalSpans
              | eval AvailabilityPercent = 100*(totalAvailability/ totalSpans)
              | fields AvailabilityPercent

 

 

 

There are some stacks that return too many events for this metric and this causes a timeout and then the search fails.

Is there a way to optimize this query to work with a lot of events?

Labels (1)
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!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...