Hi There, What version of DB Connect and Splunk were the original inputs created under, also why is there a requirement to create said inputs under a separate app? But as quick fix, as I've experienced a db migration issue before, just re-create the db input as a new input and all should work fine ... View more

Hi @rahulroy_splunk, Check mgmtHostPort configuration of your standalone instance in web.conf. https://docs.splunk.com/Documentation/Splunk/7.1.1/Admin/Webconf ... View more

I don't have a solution for the conf files but you could use my solution for DB Connect V2 via REST API https://answers.splunk.com/answers/452618/how-do-i-use-the-restful-webservices-to-setup-new.html#answer-452619 Or DB Connect V3 via conf files https://answers.splunk.com/answers/516111/splunk-db-connect-v3-automated-programmatic-creati.html#answer-516112 ... View more

Thanks! I've done just that. However, had they responded to this comment, I wouldn't have had to contact them. 😉 ... View more

I agree, v3 is where I would go, especially if the known issue about some addons not being supported doesn't affect you ... View more

My bad, missed backslashes with d. Try the updated answer... ... View more

You're probably only looking at the current app context. You need to wildcard your query to force it to look at all apps: | rest /servicesNS/-/-/saved/searches Add a filter for is_scheduled=1 to see only the scheduled jobs. See https://answers.splunk.com/answers/221242/is-there-a-way-to-identify-all-scheduled-searches.html for details. ... View more

@rahulroy_splunk: this is what i was searching for. thank you! thank you somesoni2 for your help. ... View more

This worked. ... View more