Splunk REST API - 指定警报的相对时间范围

Splunk REST API - Specify relative time range for alert

我想使用 Splunk 的 REST 创建警报 API。我希望警报获取过去两分钟内发生的事件。我该怎么做?

到目前为止,这是我的警报:

curl -k -u admin:password https://my.company:8089/servicesNS/admin/search/saved/searches \
  -d name=test7 \
  --data-urlencode output_mode='json' \
  --data-urlencode actions='' \
  --data-urlencode alert.digest_mode='1' \
  --data-urlencode alert.expires='24h' \
  --data-urlencode alert.managedBy='' \
  --data-urlencode alert.severity='3' \
  --data-urlencode alert.suppress='1' \
  --data-urlencode alert.suppress.fields='' \
  --data-urlencode alert.suppress.period='5m' \
  --data-urlencode alert.track='1' \
  --data-urlencode alert_comparator='greater than' \
  --data-urlencode alert_condition='' \
  --data-urlencode alert_threshold='10' \
  --data-urlencode alert_type='number of events' \
  --data-urlencode allow_skew='0' \
  --data-urlencode cron_schedule='*/2 * * * *' \
  --data-urlencode description='' \
  --data-urlencode disabled='0' \
  --data-urlencode displayview='' \
  --data-urlencode is_scheduled='1' \
  --data-urlencode is_visible='1' \
  --data-urlencode max_concurrent='1' \
  --data-urlencode realtime_schedule='1' \
  --data-urlencode restart_on_searchpeer_add='1' \
  --data-urlencode run_n_times='0' \
  --data-urlencode run_on_startup='0' \
  --data-urlencode schedule_priority='default' \
  --data-urlencode schedule_window='0' \
  --data-urlencode search='sourcetype="auth" failed'

您在 Splunk's documentation 中查找的参数是 dispatch.earliest_timedispatch.latest_time

这是您添加了参数的请求。它将查找最后 2 分钟内的事件:

curl -k -u admin:password https://my.company:8089/servicesNS/admin/search/saved/searches \
  -d name=test7 \
  --data-urlencode output_mode='json' \
  --data-urlencode actions='' \
  --data-urlencode alert.digest_mode='1' \
  --data-urlencode alert.expires='24h' \
  --data-urlencode alert.managedBy='' \
  --data-urlencode alert.severity='3' \
  --data-urlencode alert.suppress='1' \
  --data-urlencode alert.suppress.fields='' \
  --data-urlencode alert.suppress.period='5m' \
  --data-urlencode alert.track='1' \
  --data-urlencode alert_comparator='greater than' \
  --data-urlencode alert_condition='' \
  --data-urlencode alert_threshold='10' \
  --data-urlencode alert_type='number of events' \
  --data-urlencode allow_skew='0' \
  --data-urlencode cron_schedule='*/2 * * * *' \
  --data-urlencode description='' \
  --data-urlencode disabled='0' \
  --data-urlencode displayview='' \
  --data-urlencode is_scheduled='1' \
  --data-urlencode is_visible='1' \
  --data-urlencode max_concurrent='1' \
  --data-urlencode realtime_schedule='1' \
  --data-urlencode restart_on_searchpeer_add='1' \
  --data-urlencode run_n_times='0' \
  --data-urlencode run_on_startup='0' \
  --data-urlencode schedule_priority='default' \
  --data-urlencode schedule_window='0' \
  --data-urlencode dispatch.earliest_time='-2m' \
  --data-urlencode dispatch.latest_time='now' \
  --data-urlencode search='sourcetype="auth" failed'