Splunk Search

How to ensure upgrade of saved search, which was modified by customer and is now in local folder while customer upgrades app?

Path Finder

A customer installs version 1 of my app. Uses the Splunk Web UI to make changes to one of the saved searches. This search is now in the local folder. ($SplunkHome/etc/apps/MyApp/local). I release version 2 of my app. The customer upgrades the app. But the saved search residing in the local folder would not be updated (There would not be any local folder in my app). Other custom reports created by the customer are also present in the local folder.

One way to ensure that the saved search in local folder is upgraded is by deleting it from there. Is there any other way to achieve this?

Tags (1)
0 Karma

Path Finder

This is true for the "upgrade" process (using RPM or gz files). It is not true if you are using deployment server to push new apps. The old directory (xyz-app directory) always get deleted and push from the deployment server.
I don't know of better way of doing this!

0 Karma


Thats exactly the purpose of those folders. The local one is used for customizations, and won´t be overrided by updates, therefore the default folder is used to deploy upgrades of the default app without overwritting customizations.

So the only way would be delete custom searches, or update them manually in the local folder


Get Updates on the Splunk Community!

Get ready to show some Splunk Certification swagger at .conf24!

Dive into the deep end of data by earning a Splunk Certification at .conf24. We're enticing you again this ...

Built-in Service Level Objectives Management to Bridge the Gap Between Service & ...

Now On-Demand Join us to learn more about how you can leverage Service Level Objectives (SLOs) and the new ...

Database Performance Sidebar Panel Now on APM Database Query Performance & Service ...

We’ve streamlined the troubleshooting experience for database-related service issues by adding a database ...