This is a custom app available on Splunk enterprise instance and it needs to be moved to Splunk cloud instance. Both are different instances.
Looking for help on the process/steps that needs to be performed.
Depending on the environment setup distributed or stand alone- go to the $SPLUNK_HOME/splunk/etc/apps/my-custom-app and copy the entire folder and place it I’m the same directory of the new instance .
if it’s a distributed environment log into the deployment server and navigate to $SPLUNK_HOME/splunk/etc/deploymentapps/my-custom-app and do the same thing. Makes sure to grab the serverclass.conf as well if you created one for the app.
Depending on the environment setup distributed or stand alone- go to the $SPLUNK_HOME/splunk/etc/apps/my-custom-app and copy the entire folder and place it I’m the same directory of the new instance .
if it’s a distributed environment log into the deployment server and navigate to $SPLUNK_HOME/splunk/etc/deploymentapps/my-custom-app and do the same thing. Makes sure to grab the serverclass.conf as well if you created one for the app.
@putnamblake Thanks for the response. This custom app has a dashboard, after copying the app to the new instance, how about the data? Any suggestions? I am looking to populate the data in this new dashboard after moving to the new instance.
@Roy_9 for getting data in the UF’s that send the data would need to have the outputs.conf reconfigured to send to the new indexers/ instance or HF if that’s how you have it configured. Same process on the receiving end, edit the inputs.conf to accept from named port for the UFs. Back filling data isn’t an issue, if the host forwarding has data as far back as 1950 then when you onboard that host the data will fill also (and eat your license) if the custom app isn’t defined to only take data that’s new/ x long ago till present.