- Splunk Answers
- :
- Splunk Administration
- :
- Installation
- :
- Custom Dashboards get deleted during Splunk upgrad...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Custom Dashboards get deleted during Splunk upgrade
Is there a way to avoid the custom dashboards from getting wiped out after a Splunk upgrade or a Deployment Server restart? I tried the excludeFromUpdate option in the serverclass.conf file of the deployment server, but want to know if there is any other solution apart from that.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We finally fixed the issue by moving the app configurations to the default directory and letting customers use local directory for creating dashboards. Additionally, we have added excludeFromUpdate option for the local directory.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk puts its configurations under default directory and we are advised to add our configs under local directory.
If you have created a splunk app for aiding custom dashboard creation, then you should put your configurations under /default directory. That way when you provide further upgrades to the app, the end user created dashboards will stay unaffected.
Adding excludeFromUpdate is not the solution. This may stop you from providing updates to the app that you have created.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Strive,
We have already separated the default configurations into the default directory. We want to add excludeFromUpdate on top of that.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If the path is going to be till directory level then that should be ok.
By the way putting things under default directory alone was not sufficient?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
just moving things to default directory might work in case of new installations and not on existing upgrade ones. So we need to use a combination of both putting configurations in default directory and adding excludeFromUpdate for the local directory.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you are going to continue maintaining the local directory in your app then fine. If the solution is going to be taking out local fully and maintaining only default in the app, then it makes sense once to test without including excludeFromUpdate
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We did that and it didn't work. Hence this approach.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Upgrading Splunk should have no effect on your custom dashboards unless you put them in $SPLUNK_HOME/etc/system/default against all advice.
If this reply helps you, Karma would be appreciated.
Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...
.conf24 | Registration Open!
ICYMI - Check out the latest releases of Splunk Edge Processor
