All Apps and Add-ons

Refresh of panel that uses the Sideview HTML module

Splunk Employee
Splunk Employee

I have a dashboard that is comprised of mostly all panels that are driven by real-time searches. However, I have one panel that uses the Sideview HTML module and a real-time search will not work, as I need to control how often the content refreshes. I've tried putting a meta tag with a refresh inside of the HTML but that kicks the whole dashboard.

Is there a way to refresh just the HTML panel without redrawing the whole dashboard?

1 Solution

SplunkTrust
SplunkTrust

Well, to literally just refresh the HTML module and have it re-request it's data wouldn't do anything, because it wouldn't re-dispatch the search above.

And it sounds like you're aware of how to put refresh="60" into the <view> tag and you don't want that.

So, the alternative is basically to put an autoRefresh module in, or a Sideview CustomBehavior defined to do exactly that.

Siegfried has posted the source code for an autoRefresh module in http://splunk-base.splunk.com/answers/4263/can-you-refresh-a-single-modulechart-without-refreshing-t...

I'm going to put something to do the same thing in Sideview Utils, most likely as a sample customBehavior. It's simple enough that you could really make a dead-simple customBehavior and then not have the baggage of maintaining a whole module.

View solution in original post

SplunkTrust
SplunkTrust

Well, to literally just refresh the HTML module and have it re-request it's data wouldn't do anything, because it wouldn't re-dispatch the search above.

And it sounds like you're aware of how to put refresh="60" into the <view> tag and you don't want that.

So, the alternative is basically to put an autoRefresh module in, or a Sideview CustomBehavior defined to do exactly that.

Siegfried has posted the source code for an autoRefresh module in http://splunk-base.splunk.com/answers/4263/can-you-refresh-a-single-modulechart-without-refreshing-t...

I'm going to put something to do the same thing in Sideview Utils, most likely as a sample customBehavior. It's simple enough that you could really make a dead-simple customBehavior and then not have the baggage of maintaining a whole module.

View solution in original post