Florian Tieben
Florian Tieben
We are facing the same error and the workaround we are using is to group alerts into a module and recreate (destroy & apply) if there are bigger changes.
ok, so here is whats happening: in order to set or update the schedule_priority field you need to have the have the edit_search_schedule_priority capability in Splunk. If you dont have...
Is there a way to get more attention on this? We still have HIGH Security Warnings in our System cause of this