Relationship between Splunkweb Manager config and .conf files?

[muebel]

I have a saved search that I modified in the Splunkweb Manager. I look at the same search in the savedsearch.conf file, and the changes are not registered there. I have performed a splunk restart from the web, and the change still hasn't shown up in the .conf file.

If I run

| savedsearch "<searchname>"

it pulls up and runs the search as saved in the .conf file. However, the search is run on a schedule, and the scheduled search is following the Splunkweb configuration.

What causes the Splunkweb saved search configuration to sync up with the .conf files, and what could be stopping it from happening in this case?

[muebel]

Performed another restart after changing the Splunkweb Config for the search and it is now synced up.

[Genti · Accepted solution]

here's what i feel is happening:
First note that you might have more then just one savedsearches.conf file. The one that you are looking at is probably not the one that has the changes you submitted through splunkweb.

Check under these folders for the savedsearches.conf that reflects the changes you did:

/users/admin/search/local/savedsearches.conf or perhaps instead of admin use the user you usually login to splunk. /apps/search/local/savedsearches.conf

if youre running splunk on a unix machine you could also try running (from the splunk/etc folder) : find . -name savedsearches.conf

Usually, the changes should be instantaneous and you do not have to restart your server.
Let me know if this helped.
.gz

[gkanapathy]

Don't forget the savedsearches.conf that might be under the etc/users/ directory too.

[muebel]

The savedsearch is stored in the search app context. The changes didn't seem to be instantaneous this time, for this search.

[muebel]

I performed another restart and the Splunkweb Config reverted to what is in the .conf file. Changing Splunkweb config again...