Hi! First off, thank you for contributing your insights into the workings of the DB connect app. I have developed a collection of python3 scripts to automate adding new databases and inputs to db connect through the rest api. But I have run into the issues you describe in this post when starting the testing phase. The connections and inputs are generated in the app and are visable through the UI. The timestamp file is also present in the folder : /opt/splunk/var/lib/splunk/modinputs/server/splunk_app_db_connect/ However, the data for the inputs are not in the index. After trying the solution that you describe for this i have run into some issues that i hope someone can answer. When trying to contact the url for reloading the inputs: https://localhost:8089/servicesNS/nobody/splunk_app_db_connect/db_connect/inputs/_reload I only get a 404 status in return, leading me to think that this enpoint is no longer available through the rest api? I'm running version 3.5.1 of db connect. I can reach the : https://localhost:8089/servicesNS/nobody/search/admin/server/_reload And the task server url with curl, but not through python requests for some reason (503 error) https://localhost:8089/servicesNS/nobody/splunk_app_db_connect/db_connect/dbxproxy/taskserver But in the end the inputs generated over the api does not seem to run and i'm guessing it is becouse I dont get the reload on inputs. When running the query for the input through the UI i do get data back so i belive all parameters are present and correct for the input,identity and connection. I guess I could restart the splunk instance all togheter but that would be a last resort kind of solution that i rather avoid. Update: The data was there,just in another index then expected due to splunk baseline configs. As for the endpoints for reloading the task server, all it needed was a bit of time. If you are planning to reload the taskserver and hit the admin reload endpoint in the same script, make sure to add in breaks as it takes a couple of seconds for the service to reload and if you hit the reload task server endpoint right after the admin reload url, you will get the 503 error.
... View more