Splunk Search

Custom Chart/Bucket Span Widths?

acdevlin
Communicator

I'm trying to set up a pie chart displaying the average response time to a particular server. The pie chart should have 3 buckets of varying width, corresponding to the average response:

  • 1st bucket: 0 <= Response Time < 6

  • 2nd bucket: 6 <= Response Time < 24

  • 3rd bucket: Response Time >= 24

I am not sure how to do this in Splunk; span seems to only take fixed values in determining bucket widths. I've currently just been using chart with span=6, but it would be a huge advantage to split up the data into the 3 buckets described above.

Any help would be much appreciated.

Tags (2)
1 Solution

Ledion_Bitincka
Splunk Employee
Splunk Employee

you can try to use the rangemap command to do what you want

.... | rangemap field=ResponseTime low=0-6, middle=6-24, default=high | stats count BY range

and then display the results as a pie chart

View solution in original post

Ledion_Bitincka
Splunk Employee
Splunk Employee

you can try to use the rangemap command to do what you want

.... | rangemap field=ResponseTime low=0-6, middle=6-24, default=high | stats count BY range

and then display the results as a pie chart

acdevlin
Communicator

Perfect! Thank you very much.

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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

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