I am SOOOOO slow, or this is way too hard.
I am trying to add thirty new connections to my configuration of the Splunk DB Connect 2 app in Splunk (6.4.2).
I get the LOCAL configuration directory ({where you installed splunk}\etc\apps\splunk_app_db_connect\local ) concept and edit only those files.
I have edited the db_connections.conf file to clone a working connection and edited each cloned copy to point to the correct servers and have unique connection names. I have even edited the file security to make sure it matches the security of the other files in the same directory.
After several Splunk restarts and a full reboot, the DB Connect app still only shows the four first initial connections I created via the UI that all work.
That is when I discovered the METADATA directory ({where you installed splunk}\etc\apps\splunk_app_db_connect\metadata). I see a local.meta file and it contains the mapping of my existing connections to my INPUTS and has my desired security settings for each item.
I tried faking new entries in this file for each of my new connections (by cloning) to match a known working one. Several restarts / check file security / reboot server - no change. DB Connect still will not see my edits.
How in the *** am I supposed to bulk edit this thing to add new connections to a server? Everywhere else in the Splunk platform the initial stance is 'go edit the conf file'. This seems to be the only product so far that will only document 'in the UI, click on this'. Is that really the only way to do this? Or is there some secret arcane cache index I am supposed to know the secret handshake in order to flush it to make it read the new configuration files correctly?
↧