We have a large team of admins and users that will be using our ITSI instance. Part of our build is to move configuration from our dev environment to production. With Splunk enterprise we are used to managing everything through conf files, but it looks like we have to do it through kv stores with ITSI.
Is there another way to manage services and services templates without using the backup and restore process?
You can extract all of the required via API from your dev instance and then post for creation into your prod instance. We don’t do this often in our environment but have with some degree of success. The itsi api documentation and schema are well documented for 4.X branches.
You can extract all of the required via API from your dev instance and then post for creation into your prod instance. We don’t do this often in our environment but have with some degree of success. The itsi api documentation and schema are well documented for 4.X branches.