<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to Update Splunk after JavaScript Changes without Restarting Splunk in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-Update-Splunk-after-JavaScript-Changes-without-Restarting/m-p/257123#M16141</link>
    <description>&lt;P&gt;The better method if you are developing is to use the following setting in your web.conf. You will never have to debug refresh or bump and rarely restart.&lt;BR /&gt;
 &lt;STRONG&gt;DO NOT RUN THESE SETTINGS IN PRODUCTION&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[settings]
js_no_cache = true
cacheBytesLimit = 0
cacheEntriesLimit = 0
max_view_cache_size = 0
auto_refresh_views = 1
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Wed, 30 Nov 2016 20:01:34 GMT</pubDate>
    <dc:creator>bmacias84</dc:creator>
    <dc:date>2016-11-30T20:01:34Z</dc:date>
    <item>
      <title>How to Update Splunk after JavaScript Changes without Restarting Splunk</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-Update-Splunk-after-JavaScript-Changes-without-Restarting/m-p/257121#M16139</link>
      <description>&lt;P&gt;Hello Splunkers,&lt;/P&gt;

&lt;P&gt;I have an issue that might have an easy fix, but I do not know of one.&lt;/P&gt;

&lt;P&gt;I am working with a few teammates on a single Splunk instance. Everytime we make a javascript change to one of our reports or dashboards, we have to restart the Splunk server. This is an issue because when multiple people are working, everyone has to be at a stopping point.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Is there a way to show JavaScript or CSS changes in Splunk Web without restarting the Splunk server?&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Matt&lt;/P&gt;</description>
      <pubDate>Fri, 02 Oct 2015 16:01:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-Update-Splunk-after-JavaScript-Changes-without-Restarting/m-p/257121#M16139</guid>
      <dc:creator>mmensch</dc:creator>
      <dc:date>2015-10-02T16:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: How to Update Splunk after JavaScript Changes without Restarting Splunk</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-Update-Splunk-after-JavaScript-Changes-without-Restarting/m-p/257122#M16140</link>
      <description>&lt;P&gt;Of Course!!!!!!&lt;/P&gt;

&lt;P&gt;The easiest method is to &lt;CODE&gt;bump&lt;/CODE&gt; the server.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&lt;A href="https://&amp;lt;yourSplunk&amp;gt;/en-US/_bump" target="test_blank"&gt;https://&amp;lt;yourSplunk&amp;gt;/en-US/_bump&lt;/A&gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Click that button. Every click increases the bump, which effectively breaks all caching in the webserver. No need to restart! If you find it doesn't work as expected, run also the &lt;CODE&gt;debug/refresh&lt;/CODE&gt; endpoint.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&lt;A href="https://&amp;lt;yourSplunk&amp;gt;/debug/refresh" target="test_blank"&gt;https://&amp;lt;yourSplunk&amp;gt;/debug/refresh&lt;/A&gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And if that doesn't work, restart the web service only.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; $SPLUNK_HOME/bin/splunk restart splunkweb
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And if that doesn't work, restart Splunk.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Oct 2015 16:22:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-Update-Splunk-after-JavaScript-Changes-without-Restarting/m-p/257122#M16140</guid>
      <dc:creator>alacercogitatus</dc:creator>
      <dc:date>2015-10-02T16:22:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to Update Splunk after JavaScript Changes without Restarting Splunk</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-Update-Splunk-after-JavaScript-Changes-without-Restarting/m-p/257123#M16141</link>
      <description>&lt;P&gt;The better method if you are developing is to use the following setting in your web.conf. You will never have to debug refresh or bump and rarely restart.&lt;BR /&gt;
 &lt;STRONG&gt;DO NOT RUN THESE SETTINGS IN PRODUCTION&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[settings]
js_no_cache = true
cacheBytesLimit = 0
cacheEntriesLimit = 0
max_view_cache_size = 0
auto_refresh_views = 1
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 30 Nov 2016 20:01:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-Update-Splunk-after-JavaScript-Changes-without-Restarting/m-p/257123#M16141</guid>
      <dc:creator>bmacias84</dc:creator>
      <dc:date>2016-11-30T20:01:34Z</dc:date>
    </item>
    <item>
      <title>Re: How to Update Splunk after JavaScript Changes without Restarting Splunk</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-Update-Splunk-after-JavaScript-Changes-without-Restarting/m-p/257124#M16142</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;

&lt;P&gt;i created a custom search command "| dobump ". Feel free to test it out and give feedback.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://github.com/schose/TA-dobump"&gt;https://github.com/schose/TA-dobump&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Cheers,&lt;/P&gt;

&lt;P&gt;Andreas&lt;/P&gt;</description>
      <pubDate>Wed, 02 Oct 2019 06:04:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-Update-Splunk-after-JavaScript-Changes-without-Restarting/m-p/257124#M16142</guid>
      <dc:creator>schose</dc:creator>
      <dc:date>2019-10-02T06:04:37Z</dc:date>
    </item>
  </channel>
</rss>

