Dashboards & Visualizations

How to show single value in chart

allansneddon
Explorer

I currently have this query:

index="network_services" sourcetype="emails" spam_status=positive | timechart span=1d count | delta count as Delta | fillnull value=0 Delta | eval Total=count-Delta | eval percIncrDecr=(Delta/Total)*100 |

I would like my chart to show only the percIncrDecr, at the moment it shows count, delta, Total and percincrdecr. Is there a way to show only the one variable?

Cheers,

Allan

Tags (1)
0 Karma
1 Solution

niketn
Legend

You have two options to achieve this.

1) Filter unwanted fields in SPL using fields command

 index="network_services" sourcetype="emails" spam_status=positive 
| timechart span=1d count 
| delta count as Delta 
| fillnull value=0 Delta 
| eval Total=count-Delta 
| eval percIncrDecr=(Delta/Total)*100 
| fields - count Delta Total

2) Using Chart Configuration charting.chart.fieldHideList

<option name="charting.chart.fieldHideList">["count","Delta","Total"]</option>

PS: Only advantage of the second would be that the field will be hidden fron display however, you can still code them for Chart Drilldown. If you don't need these fields at all then it is better to filter them through query in the first approach.

____________________________________________
| makeresults | eval message= "Happy Splunking!!!"

View solution in original post

niketn
Legend

You have two options to achieve this.

1) Filter unwanted fields in SPL using fields command

 index="network_services" sourcetype="emails" spam_status=positive 
| timechart span=1d count 
| delta count as Delta 
| fillnull value=0 Delta 
| eval Total=count-Delta 
| eval percIncrDecr=(Delta/Total)*100 
| fields - count Delta Total

2) Using Chart Configuration charting.chart.fieldHideList

<option name="charting.chart.fieldHideList">["count","Delta","Total"]</option>

PS: Only advantage of the second would be that the field will be hidden fron display however, you can still code them for Chart Drilldown. If you don't need these fields at all then it is better to filter them through query in the first approach.

____________________________________________
| makeresults | eval message= "Happy Splunking!!!"
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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...