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
A conditional recipient rule composed of a ``scope`` (the matching condition) and
41
+
``recipients`` (who to notify when it matches).
41
42
42
43
:param recipients: A list of recipients to notify. Uses the same format as the monitor ``message`` field. Must not start with an '@'. Cannot be used with ``conditional_recipients``.
43
44
:type recipients: [str]
44
45
45
-
:param scope: The scope to which the monitor applied.
46
+
:param scope: Defines the condition under which the recipients are notified. Supported formats:
47
+
48
+
* Monitor status condition using ``transition_type:<status>`` , for example ``transition_type:is_alert``.
49
+
* A single tag key:value pair, for example ``env:prod``.
Copy file name to clipboardExpand all lines: src/datadog_api_client/v2/model/monitor_notification_rule_filter_scope.py
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -34,9 +34,9 @@ def openapi_types(_):
34
34
35
35
def__init__(self_, scope: str, **kwargs):
36
36
"""
37
-
Filter monitor notifications. A monitor notification must match the scope.
37
+
Filters monitor notifications using a scope expression over key:value pairs with boolean logic (AND, OR, NOT).
38
38
39
-
:param scope: A scope composed of one or several key:value pairs, which can be used to filter monitor notifications on monitor and group tags.
39
+
:param scope: A scope expression composed by key:value pairs (e.g. ``service:foo`` ) with boolean operators (AND, OR, NOT) and parentheses for grouping.
0 commit comments