Dashboards & Visualizations

How to Update Splunk after JavaScript Changes without Restarting Splunk

mmensch
Path Finder

Hello Splunkers,

I have an issue that might have an easy fix, but I do not know of one.

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.

Is there a way to show JavaScript or CSS changes in Splunk Web without restarting the Splunk server?

Thanks,
Matt

1 Solution

alacercogitatus
SplunkTrust
SplunkTrust

Of Course!!!!!!

The easiest method is to bump the server.

https://<yourSplunk>/en-US/_bump

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 debug/refresh endpoint.

https://<yourSplunk>/debug/refresh

And if that doesn't work, restart the web service only.

 $SPLUNK_HOME/bin/splunk restart splunkweb

And if that doesn't work, restart Splunk.

View solution in original post

schose
Builder

Hi,

i created a custom search command "| dobump ". Feel free to test it out and give feedback.

https://github.com/schose/TA-dobump

Cheers,

Andreas

bmacias84
Champion

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.
DO NOT RUN THESE SETTINGS IN PRODUCTION

[settings]
js_no_cache = true
cacheBytesLimit = 0
cacheEntriesLimit = 0
max_view_cache_size = 0
auto_refresh_views = 1

alacercogitatus
SplunkTrust
SplunkTrust

Of Course!!!!!!

The easiest method is to bump the server.

https://<yourSplunk>/en-US/_bump

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 debug/refresh endpoint.

https://<yourSplunk>/debug/refresh

And if that doesn't work, restart the web service only.

 $SPLUNK_HOME/bin/splunk restart splunkweb

And if that doesn't work, restart Splunk.

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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...