Dashboards & Visualizations

Bar Graph/Timechart show multiple values for same field and remove whitespace from graph

tbrown
Path Finder

I have events which are transactions. I've extracted a field from these events which are the site they come from. Basically, I want to make a bar graph/timechart/chart that shows the duration of each of these transactions, separated by the site they come from. I don't want to use the avg() or sum() or max() options for a chart/timechart because I want every event to appear on the graph, I don't want to only show the max() for each site.

I've tried a timechart using "cont=false" but that didn't work because it still automatically grouped certain events together. I've tried "stats count by Site, duration", and while that works, it still shows the count bars on the graph, and I don't want that, and it also doesn't group them according to time (even if I use "| sort -_time")

 

Labels (4)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

something like this?

| makeresults
| eval _raw="site,tr,duration
A,a001,100
A,a002,10
B,b001,50
C,c001,25
B,b002,14
C,c002,22"
| multikv forceheader=1 
| rename COMMENT as "sample data generation"
| chart values(duration) as duration over site by tr

r. Ismo 

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!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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