#SPLUNK SHOWHIDE PANEL SIDEVIEW UPDATE#
#SPLUNK SHOWHIDE PANEL SIDEVIEW CODE#

Now, you can click and drag to adjust table column widths, in both View and Edit modes! In the example above, you can see that the 'sourcetype' column is wider than it needs to be, while the 'source' column could use some more space. For Table visualizations, you can also choose whether you want your font spacing to be proportional or monospaced. In the configuration panel, look for the 'Font Size' option, and adjust anywhere between Extra Small and Extra Large. This has been one of the top requests this year, and we're excited to finally ship it.

#SPLUNK SHOWHIDE PANEL SIDEVIEW UPDATE#

The first update that I'm happy to announce is that you can now control font size in Table and Markdown visualizations.

Enhanced security by informing users before leaving a Splunk dashboard.

Ability to edit permissions while viewing a Studio dashboard.

Additional metadata support for search-based tokens.

Improved status messages and placeholder images.

Font size control for Tables and Markdown.In Splunk Cloud Platform, we've included a handful of Dashboard Studio 'little things' updates: Sometimes it's big things - such as being able to set tokens on drilldowns - and sometimes it's little things. 's always interesting to hear what feature requests dashboard users share with our product team. =/ (Yes autoRun is very strange but if you follow the rule of only ever having one, and always having it at the top, almost all of the strangeness goes away)ģ) and thirdly, here's a slightly cleaner version of your JS function that you may find useful. With the autoRun='true' on the Search module, the very first push on page load doesn't hide the checkbox because nobody has pushed the TimeRangePicker's data downstream yet. IN this case you should move it up to the TimeRangePicker and not have any autoRun on the Search module. It actually tells any module 'when the page loads, start pushing data to all downstream from this point', and as such it should always be up at the top of the hierarchy. You have an autoRun='True' but you've made a common mistake which is to put it on the Search module thinking it tells the Search module to run it's search. For the second you meant to check the getLatestTimeTerms not getEarliestTimeTerms.Ĭhanging that alone gets it to mostly work.Ģ) There is also a second lesser problem though. Now the checkbox goes away as soon as I change the time range and never comes back regardless of the setting.ġ) The main problem is that your if statement is only firing if the earliest time term is and also the earliest time term is 'now'.

If & this.getContext().get('search').getTimeRange().getEarliestTimeTerms()='now')Īnd yes, I rebooted splunkweb to make sure application.js has been read by splunk after my change.ĮDIT: I just found 2 errors, thanks to google developper tools.ġ- there was a brace missing in my javascript.Ģ- I needed to get the context from 'this'. Var methodReference = (checkBoxModule) ĬheckBoxModule.onContextChange = function() ('LRO_ShowAutoRefreshCheckBox', function(checkBoxModule)

#SPLUNK SHOWHIDE PANEL SIDEVIEW CODE#

But it's all there.Īnd here is the code I added in application.js: OK the code looks partly marked as code partly as regular comments.

Index=os * | rex 'lvn-(?)-' | dedup Line | table Line | sort Line

įor 5 mins auto-refresh select the 'Last 60 minutes' time range. It should only be visible when the user selects 'Last 60 minutes' in the TimeRangePicker. The checkbox remains visible regardless of the time range I select.

I wrote the code below after looking at many examples, and reviewing the modules documentation.Īnd yet, I can't get it to work.

Splunk showhide panel sideview