Can this warning be ignored coz I always get this in the SH Cluster. We do not have scheduled inputs and scheduled outputs and thus we did not install the DB Connect app on the Heavy forwarders. We have it only the SH cluster.
But everytime I open the app , I see this warning. So can This be ignored or is there a way to get rid of this? Is it mandatory to install the app on the Heavy Forwarders?
As far as it is documented, there is no way to hide the message: http://docs.splunk.com/Documentation/DBX/latest/DeployDBX/WhatsnewinSplunkDBConnect#Scheduled_tasks_...
Perhaps an alternative approach is to disable the visibility of the app for non-admins. That way the commands you want to use are available globally but the app itself is invisible other than for admins who know to ignore the message.
Make the app invisible: http://docs.splunk.com/Documentation/Splunk/latest/Admin/Managingappconfigurationsandproperties
Make sure the command have global permissions: http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Manageknowledgeobjectpermissions#Make_a...
As far as it is documented, there is no way to hide the message: http://docs.splunk.com/Documentation/DBX/latest/DeployDBX/WhatsnewinSplunkDBConnect#Scheduled_tasks_...
Perhaps an alternative approach is to disable the visibility of the app for non-admins. That way the commands you want to use are available globally but the app itself is invisible other than for admins who know to ignore the message.
Make the app invisible: http://docs.splunk.com/Documentation/Splunk/latest/Admin/Managingappconfigurationsandproperties
Make sure the command have global permissions: http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Manageknowledgeobjectpermissions#Make_a...
Thankyou Burch 🙂
NP! If you found that satisfactory, then please mark it as an accepted answer so others who stumble on this question will see there is a potential solution. If not, then leave it as is of course.
I guess if we keep an app as invisible, it goes invisible to every role including admin as well.
Hmmm. I think it depends on if you removed the read permission for that role...