We have migrated our settings from a standalone Splunk search head (views, users, etc) to a search head cluster. We copied search to search_migrated app and did export=system in metadata/local.meta.
Our problem is that we need the search_migrated app to remain visible so that the views are also visible. In that regard, everything is working as expected. The issue arises when we try to do a search from the search_migrated app. The header is replaced by the "Website monitoring" app's header, and if we select "search_migrated" from the app drop-down it just brings us to the Website Monitoring app.
Is there a way to separate the function of these two apps?
We tested the SHC and Indexer clustering with this app. What I found was to spin up a separate SH instance that was standalone and use it as an app server. We installed the Website_monitoring app there and configured an app to forward all data to our Relay Forwarders. What happens then is that all configuration of the app happens only on that standalone SH. It then replicates out to all of the other SH's in the cluster. You will be able to create dashboards for this app on all of the SH's. If you want to use a new index for this, make sure you create it before you install (or in your case, reinstall) the app, as the data flow is one-way from standalone SH to the cluster.
You should seriously just consider reinstalling the app, unless you already have hundreds of websites in there.