Splunk v9.3 not refreshing nav correctly

[schose]

Hi all,

Since v9.3 there seem to be a different method for displaying nav menus. When you update the tag <label> tag of a view from external editor, those changes are not updated in navigation until a local storage object is deleted. 

/debug/refresh or restart splunk doesn't refresh the navigation. 

I was able to to update navigation when deleting the following object -> chrome -> developer tools -> applications -> "local storage" -> 

splunk-appnav:MYAPP:admin:en-GB:UUID containing the following datastructure.. 

{
  "nav": [
    {
      "label": "Search",
      "uri": "/en-GB/app/testapp/search",
      "viewName": "search",
      "isDefault": true
    },
    {
      "label": "testview",
      "uri": "/en-GB/app/testapp/testview",
      "viewName": "testview"
    }
  ],
  "color": null,
  "searchView": "search",
  "lastModified": 1727698963355
}

I'm wondering why content of the nav is now saved on client side. This is a different behaviour than on v9.1 and v9.2. If i need to guess, they tried to improve response time of the webui.

But how do i ensure that every user is receiving the latest version of navigation menu in an app? 

Best regards,

Andreas

[wgawhh5hbnht]

Hi @schose 
Were you able to resolve the issue of the navigation menu labels updating? I'm running into the same issue.

[isoutamo]

In slack there have been discussions that staring of 9.3.x some user preferences have moved into kvstore. Unfortunately that is not documented. I’m not sure if that affect also in this case, but I suggest that you will create a support case for Splunk.

[marnall]

In web.conf, there are some cache-related settings that might work to disable either the caching of views, or the cache entirely. https://docs.splunk.com/Documentation/Splunk/latest/Admin/Webconf

max_view_cache_size = <integer>
* The maximum number of views to cache in the appserver.
* Default: 1000

cacheBytesLimit = <integer>
* Splunkd can keep a small cache of static web assets in memory.
When the total size of the objects in cache grows larger than this setting,
in bytes, splunkd begins ageing entries out of the cache.
* If set to zero, disables the cache.
* Default: 4194304

[schose]

Hi @marnall ,

I had set web.conf to

[settings]
cacheEntriesLimit = 0
cacheBytesLimit = 0
js_no_cache = 1

.. no difference. 

[marnall]

That's very strange, as cacheEntriesLimit should disable the cache, thus forcing all clients to re-load static assets. Can you confirm that the setting is used, using btool?