Deployment Architecture

Promoting an app from private visibility to app visibility does not propagate across the search head cluster


I have a 6 member search head cluster v6.2.2. A user promoted their dashboard from private to app level visibility. On one server, the dashboard appears with app level visibility and on the other 5 it doesn't appear at all. On one where it doesn't appear in the 'Dashboards' link, it does appear in the 'Settings|User Interface|Views' page--as private. There is no app level version. BTW, the app has r/w permissions for all.

It seems mighty tedious if every modification to a dashboard has to be done using the deployer. How could that be even managed?

What might I be missing?

0 Karma

Splunk Employee
Splunk Employee

You are on Search Head Cluster and the behavior described here has been identified as Splunk Bug #
SPL-98917/ SPL-99099:[SHPNEXT] to figure out a way to migrate private user assets into a search head cluster such that they can be deleted, moved, shared, etc

This Bug is expected to be fixed in Splunk release 6.2.4, in the mean time please log a Support Case an Support has script to fix this issue.

0 Karma
Get Updates on the Splunk Community!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...