You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have, relatively recently, been using the splunk_saved_searches resource to create alerts. However this no longer appears we work. It will always create the saved search as a "Report" rather than an "Alert" - even if the correct attributes are set that should create it as an alert.
For example this simple resource should, and previously would have created an "Alert"
I have tested many combinations of attributes such as alert_digest_mode, alert_type, alert_track and is_scheduled however all have the same result - creating a Report rather than an Alert.
Indeed alerts we have previously created using Terraform have been reverted to reports.
I also cannot create the alert/saved search. It throws the following error:
Error: 400 Bad Request: {"messages":[{"type":"ERROR","text":"windowed real-time per result alerts require field based alert throttling to be enabled"}]}
I'm trying to pass alert_type as number of events. One colleague told me it only works by creating as an always running alarm:
Affected Resource(s)
splunk_saved_searches
Description
We have, relatively recently, been using the
splunk_saved_searches
resource to create alerts. However this no longer appears we work. It will always create the saved search as a "Report" rather than an "Alert" - even if the correct attributes are set that should create it as an alert.For example this simple resource should, and previously would have created an "Alert"
I have tested many combinations of attributes such as
alert_digest_mode
,alert_type
,alert_track
andis_scheduled
however all have the same result - creating a Report rather than an Alert.Indeed alerts we have previously created using Terraform have been reverted to reports.
Versions
The text was updated successfully, but these errors were encountered: