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
Copy file name to clipboardExpand all lines: services/observability/src/stackit/observability/models/create_alert_config_receiver_payload_email_configs_inner.py
+14-2Lines changed: 14 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@
18
18
importpprint
19
19
fromtypingimportAny, ClassVar, Dict, List, Optional, Set
Copy file name to clipboardExpand all lines: services/observability/src/stackit/observability/models/create_alert_config_receiver_payload_opsgenie_configs_inner.py
+17-3Lines changed: 17 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@
18
18
importpprint
19
19
fromtypingimportAny, ClassVar, Dict, List, Optional, Set
Copy file name to clipboardExpand all lines: services/observability/src/stackit/observability/models/create_alert_config_receiver_payload_web_hook_configs_inner.py
+9-2Lines changed: 9 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -32,11 +32,14 @@ class CreateAlertConfigReceiverPayloadWebHookConfigsInner(BaseModel):
32
32
description="Microsoft Teams webhooks require special handling. If you set this property to true, it is treated as such",
33
33
alias="msTeams",
34
34
)
35
+
send_resolved: Optional[StrictBool] =Field(
36
+
default=True, description="Whether to notify about resolved alerts.", alias="sendResolved"
description="The labels by which incoming alerts are grouped together. For example, multiple alerts coming in for cluster=A and alertname=LatencyHigh would be batched into a single group. To aggregate by all possible labels use the special value '...' as the sole label name, for example: group_by: ['...']. This effectively disables aggregation entirely, passing through all alerts as-is. This is unlikely to be what you want, unless you have a very low alert volume or your upstream notification system performs its own grouping.",
@@ -71,6 +76,7 @@ class CreateAlertConfigRoutePayload(BaseModel):
71
76
default=None, description="Zero or more child routes."
description="The labels by which incoming alerts are grouped together. For example, multiple alerts coming in for cluster=A and alertname=LatencyHigh would be batched into a single group. To aggregate by all possible labels use the special value '...' as the sole label name, for example: group_by: ['...']. This effectively disables aggregation entirely, passing through all alerts as-is. This is unlikely to be what you want, unless you have a very low alert volume or your upstream notification system performs its own grouping.",
@@ -71,6 +76,7 @@ class UpdateAlertConfigRoutePayload(BaseModel):
71
76
default=None, description="Zero or more child routes."
0 commit comments