Dashboards & Visualizations

Y-Axis Based on Field Values

PaintItParker
Explorer

I have a field, SecondsSpentExecuting. A logged event will have that field. I want to visualize my data with a line chart, so the x-axis is _time, and the y-axis is SecondsSpentExecuting, so for a given event, at a given time on the x-axis, you see on the y-axis visually how long it took compared to other events in that line chart.

The current command I am using is:

timechart count by SecondsSpentExecuting

But in this case, the y-axis is the quantity of events that spent x seconds executing, so it does not work for my purposes.

How could I write a command which considers the actual value of the SecondsSpentExecuting field rather than charting by quantity of events?

Labels (2)
0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust
| gentimes start=-1 increment=10m 
| eval SecondsSpentExecuting=random() % 50
| rename starttime as _time 
| fields - endhuman endtime starthuman


| table _time SecondsSpentExecuting

View solution in original post

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust
| gentimes start=-1 increment=10m 
| eval SecondsSpentExecuting=random() % 50
| rename starttime as _time 
| fields - endhuman endtime starthuman


| table _time SecondsSpentExecuting
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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...