Before I upgrade to 6.3, wanted to be sure that Sideview Utils 3.2.7 is compatible.
Thanks
It should be fine. However 3.2.7 is a year and a half old and I recommend upgrading to the most recent Sideview Utils (3.3.8)
Release notes are here - http://sideviewapps.com/apps/sideview-utils/release-notes/
and you can add yourself to the release notes mailing list here - http://sideviewapps.com/apps/sideview-utils/mailing-list/ Your email will never end up anywhere else and you wont get any emails out of it besides the dry little release-notes email for every maintenance release.
I tried Sideview Utils 6.3.11 with Splunk 6.3.6. The Sideview Utils App Window in splunk displays blank page. Only panel layouts are seen in it.,I tried Sideview Utils 3.3.11 with splunk 6.3.6. Sideview Utill App Window in splunk is blank. Only panel layout is seen nothing else ...
Hm. Very strange and I don't know of anyone else seeing this.
1) Did you restart the server after installing the app? If not, does restarting now fix it?
2) Did you clear your browser cache after installing the app? Or click the button on the "bump" endpoint? If not does navigating to http://YOUR_HOST:8000/en-US/_bump and clicking the grey button fix the problem?
3) If you open the "error console" of your app are there any javascript errors displaying?
I did restart my server and no error messages displayed. I dint try the step 2. As I was in a hurry to give my reports I re-installed Splunk 6.2.2 and completed my work. Will update you while I try again with Splunk 6.3.6. Thank you.
It worked after clicking the grey button. Thank you 🙂
Excellent. Thank you very much for posting back on here that the Bump button worked. Splunk's static file cacheing is relatively complicated, and you're really not supposed to ever need to click the Bump button like this. However even in this day and age there seem to be corner cases where app upgrades lead to some mismatched static files (after upgrade and restart some are still cached and some are refreshed). In such cases the Bump button is the "bigger hammer"
This sounds like something I saw once with an ad blocker blocking part of splunk's javascript. Once I whitelisted splunk, problem went away