fix: Anomaly alert example

Signed-off-by: Federico Barcelona <[email protected]>

Author: tembleking

examples/alert.tf

@@ -6,6 +6,8 @@ resource "sysdig_monitor_alert_anomaly" "sample" {
 
   monitor = ["cpu.used.percent", "memory.bytes.used"]
 
+  trigger_after_minutes = 10
+
   multiple_alerts_by = ["kubernetes.cluster.name",
     "kubernetes.namespace.name",
     "kubernetes.deployment.name",

website/docs/r/sysdig_monitor_alert_anomaly.html.markdown

@@ -22,6 +22,8 @@ resource "sysdig_monitor_alert_anomaly" "sample" {
 
 	monitor = ["cpu.used.percent", "memory.bytes.used"]
 
+    trigger_after_minutes = 10
+
 	multiple_alerts_by = ["kubernetes.cluster.name", 
                           "kubernetes.namespace.name", 
                           "kubernetes.deployment.name", 
@@ -67,4 +69,4 @@ In addition to all arguments above, the following attributes are exported, which
 alerts in Sysdig Monitor:
 
 * `version` - Current version of the resource in Sysdig Monitor.
-* `team` - Team ID that owns the alert.
+* `team` - Team ID that owns the alert.