Configure Splunk AI Assistant for SPL
If you have administrator permissions, you can use the Settings tab of Splunk AI Assistant for SPL to configure both data sharing and the personalization preview.
Configure share data settings
Configure personalization preview settings
Beginning with version 1.0.5, the assistant offers a preview of a personalization feature. The personalization feature uses your data to provide better results from Splunk AI Assistant for SPL.
Only users with administrator privileges can opt-in or opt-out of this preview. You can opt-in or out at any time. Whether the preview is turned off or on, that setting applies at the app level, across all users, and not at the individual user level.
If you want to opt-in or out of this preview feature, navigate to the Settings tab of the assistant. Select or de-select the Share search history, indexes, and sourcetypes with Splunk option, as shown in the following image:
Users without administrator privileges see the Personalization information on the Settings tab, and the setting chosen, but cannot change this setting.
If you opt-in for the personalization preview, collected data is stored in the vector database. If you opt-out of this personalization preview at a later date, a cleanup job runs weekly which deletes any collected data.
To learn more about this personalization preview, see Feature preview: Personalization.
Deleting data used by the assistant
Splunk AI Assistant for SPL keeps the data used to power the service within the Splunk platform environment while running the service. Regardless of if you stay opted in or choose to opt out of sharing data collected for research and development, the assistant uses your data to power the Splunk AI Assistant for SPL service.
For information on data collected for research and development, see Share data in Splunk AI Assistant for SPL.
If you need the data collected for research and development deleted, you must open a technical support ticket. Otherwise this data is deleted if your Splunk Cloud Platform subscription is de-provisioned.
Chat data is stored in the KVStore on the customer's stack. If you choose to delete a chat, that chat data is deleted from your local KVStore collection.