We follow all steps and install addon by using instance Search Head on Splunk Entreprise version.
But we did not see any data when performing searching, it’s always empty.
Which type of instance did you test ? in organization name field off addon configuration and data input configuration which value must be used (tenant /org name or full api url ) ?
After long hours of debugging, I was able to resolve the issue by performing the following actions:
Removed the DATETIME_CONFIG parameter from the file “$SplunkHome/etc/apps/TA-sailpoint-identitynow-auditevent-add-on/default/props.conf”.
Added the following elements to the file “etc/apps/TA-sailpoint-identitynow-auditevent-add-on/local/ta_sailpoint_identitynow_auditevent_add_on_settings.conf”:
[proxy]
proxy_password = NONE
proxy_type =
@colin_mckibben may be you can transfert this elements to your team who are developped this plugin may be they have an explanation.
Thanks for your effort in finding the root cause @baoussounda!
Sailpoint team: we are on the Cloud version of Splunk so cannot use this workaround. Someone needs to update the add-on on your end. This is critical for us since we are missing auditable events.
We were experiencing the same issue. Sailpoint support let us know that version 2.0.14 of the app was just released on 8/23/24 to fix this issue, and we can install it successfully on Splunk Enterprise but our Splunk Cloud environment is not showing any update available from 2.0.13. We tried fully uninstalling 2.0.13 and installing from Splunkbase (which shows 2.0.14 as compatible with Cloud) and it pulls down 2.0.13 again. Anyone else experiencing this issue? Has anyone else been able to install 2.0.14 on Splunk Cloud?