pulumi-signalfx 7.2.0a1709367777__py3-none-any.whl → 7.6.0a1736835428__py3-none-any.whl

pulumi_signalfx/slo.py

@@ -4,9 +4,14 @@
 
 import copy
 import warnings
+import sys
 import pulumi
 import pulumi.runtime
 from typing import Any, Mapping, Optional, Sequence, Union, overload
+if sys.version_info >= (3, 11):
+    from typing import NotRequired, TypedDict, TypeAlias
+else:
+    from typing_extensions import NotRequired, TypedDict, TypeAlias
 from . import _utilities
 from . import outputs
 from ._inputs import *
@@ -23,12 +28,11 @@ class SloArgs:
                  name: Optional[pulumi.Input[str]] = None):
         """
         The set of arguments for constructing a Slo resource.
-        :param pulumi.Input['SloInputArgs'] input: SignalFlow program and arguments text strings that define the streams used as successful event count and total event
-               count
+        :param pulumi.Input['SloInputArgs'] input: Properties to configure an SLO object inputs
         :param pulumi.Input['SloTargetArgs'] target: Define target value of the service level indicator in the appropriate time period.
-        :param pulumi.Input[str] type: Type of the SLO. Currently only RequestBased SLO is supported
-        :param pulumi.Input[str] description: Description of the SLO
-        :param pulumi.Input[str] name: Name of the SLO
+        :param pulumi.Input[str] type: Type of the SLO. Currently just: `"RequestBased"` is supported.
+        :param pulumi.Input[str] description: Description of the SLO.
+        :param pulumi.Input[str] name: Name of the SLO. Each SLO name must be unique within an organization.
         """
         pulumi.set(__self__, "input", input)
         pulumi.set(__self__, "target", target)
@@ -42,8 +46,7 @@ class SloArgs:
     @pulumi.getter
     def input(self) -> pulumi.Input['SloInputArgs']:
         """
-        SignalFlow program and arguments text strings that define the streams used as successful event count and total event
-        count
+        Properties to configure an SLO object inputs
         """
         return pulumi.get(self, "input")
 
@@ -67,7 +70,7 @@ class SloArgs:
     @pulumi.getter
     def type(self) -> pulumi.Input[str]:
         """
-        Type of the SLO. Currently only RequestBased SLO is supported
+        Type of the SLO. Currently just: `"RequestBased"` is supported.
         """
         return pulumi.get(self, "type")
 
@@ -79,7 +82,7 @@ class SloArgs:
     @pulumi.getter
     def description(self) -> Optional[pulumi.Input[str]]:
         """
-        Description of the SLO
+        Description of the SLO.
         """
         return pulumi.get(self, "description")
 
@@ -91,7 +94,7 @@ class SloArgs:
     @pulumi.getter
     def name(self) -> Optional[pulumi.Input[str]]:
         """
-        Name of the SLO
+        Name of the SLO. Each SLO name must be unique within an organization.
         """
         return pulumi.get(self, "name")
 
@@ -110,12 +113,11 @@ class _SloState:
                  type: Optional[pulumi.Input[str]] = None):
         """
         Input properties used for looking up and filtering Slo resources.
-        :param pulumi.Input[str] description: Description of the SLO
-        :param pulumi.Input['SloInputArgs'] input: SignalFlow program and arguments text strings that define the streams used as successful event count and total event
-               count
-        :param pulumi.Input[str] name: Name of the SLO
+        :param pulumi.Input[str] description: Description of the SLO.
+        :param pulumi.Input['SloInputArgs'] input: Properties to configure an SLO object inputs
+        :param pulumi.Input[str] name: Name of the SLO. Each SLO name must be unique within an organization.
         :param pulumi.Input['SloTargetArgs'] target: Define target value of the service level indicator in the appropriate time period.
-        :param pulumi.Input[str] type: Type of the SLO. Currently only RequestBased SLO is supported
+        :param pulumi.Input[str] type: Type of the SLO. Currently just: `"RequestBased"` is supported.
         """
         if description is not None:
             pulumi.set(__self__, "description", description)
@@ -132,7 +134,7 @@ class _SloState:
     @pulumi.getter
     def description(self) -> Optional[pulumi.Input[str]]:
         """
-        Description of the SLO
+        Description of the SLO.
         """
         return pulumi.get(self, "description")
 
@@ -144,8 +146,7 @@ class _SloState:
     @pulumi.getter
     def input(self) -> Optional[pulumi.Input['SloInputArgs']]:
         """
-        SignalFlow program and arguments text strings that define the streams used as successful event count and total event
-        count
+        Properties to configure an SLO object inputs
         """
         return pulumi.get(self, "input")
 
@@ -157,7 +158,7 @@ class _SloState:
     @pulumi.getter
     def name(self) -> Optional[pulumi.Input[str]]:
         """
-        Name of the SLO
+        Name of the SLO. Each SLO name must be unique within an organization.
         """
         return pulumi.get(self, "name")
 
@@ -181,7 +182,7 @@ class _SloState:
     @pulumi.getter
     def type(self) -> Optional[pulumi.Input[str]]:
         """
-        Type of the SLO. Currently only RequestBased SLO is supported
+        Type of the SLO. Currently just: `"RequestBased"` is supported.
         """
         return pulumi.get(self, "type")
 
@@ -196,9 +197,9 @@ class Slo(pulumi.CustomResource):
                  resource_name: str,
                  opts: Optional[pulumi.ResourceOptions] = None,
                  description: Optional[pulumi.Input[str]] = None,
-                 input: Optional[pulumi.Input[pulumi.InputType['SloInputArgs']]] = None,
+                 input: Optional[pulumi.Input[Union['SloInputArgs', 'SloInputArgsDict']]] = None,
                  name: Optional[pulumi.Input[str]] = None,
-                 target: Optional[pulumi.Input[pulumi.InputType['SloTargetArgs']]] = None,
+                 target: Optional[pulumi.Input[Union['SloTargetArgs', 'SloTargetArgsDict']]] = None,
                  type: Optional[pulumi.Input[str]] = None,
                  __props__=None):
         """
@@ -206,134 +207,85 @@ class Slo(pulumi.CustomResource):
 
         To learn more about this feature take a look on [documentation for SLO](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/slo-intro.html).
 
-        ## Notification format
-
-        As Splunk Observability Cloud supports different notification mechanisms, use a comma-delimited string to provide inputs. If you want to specify multiple notifications, each must be a member in the list, like so:
+        ## Example
 
         ```python
         import pulumi
+        import pulumi_signalfx as signalfx
+
+        foo_service_slo = signalfx.Slo("foo_service_slo",
+            name="foo service SLO",
+            type="RequestBased",
+            description="SLO monitoring for foo service",
+            input={
+                "program_text": \"\"\"G = data('spans.count', filter=filter('sf_error', 'false') and filter('sf_service', 'foo-service'))
+        T = data('spans.count', filter=filter('sf_service', 'foo-service'))\"\"\",
+                "good_events_label": "G",
+                "total_events_label": "T",
+            },
+            target={
+                "type": "RollingWindow",
+                "slo": 95,
+                "compliance_period": "30d",
+                "alert_rules": [{
+                    "type": "BREACH",
+                    "rules": [{
+                        "severity": "Warning",
+                        "notifications": ["Email,foo-alerts@bar.com"],
+                    }],
+                }],
+            })
         ```
 
+        ## Notification format
+
+        As Splunk Observability Cloud supports different notification mechanisms, use a comma-delimited string to provide inputs. If you want to specify multiple notifications, each must be a member in the list, like so:
+
         See [Splunk Observability Cloud Docs](https://dev.splunk.com/observability/reference/api/detectors/latest) for more information.
 
         Here are some example of how to configure each notification type:
 
         ### Email
 
-        ```python
-        import pulumi
-        ```
-
         ### Jira
 
         Note that the `credentialId` is the Splunk-provided ID shown after setting up your Jira integration. See also `jira.Integration`.
 
-        ```python
-        import pulumi
-        ```
-
         ### OpsGenie
 
         Note that the `credentialId` is the Splunk-provided ID shown after setting up your Opsgenie integration. `Team` here is hardcoded as the `responderType` as that is the only acceptable type as per the API docs.
 
-        ```python
-        import pulumi
-        ```
-
         ### PagerDuty
 
-        ```python
-        import pulumi
-        ```
-
         ### Slack
 
         Exclude the `#` on the channel name:
 
-        ```python
-        import pulumi
-        ```
-
         ### Team
 
         Sends [notifications to a team](https://docs.signalfx.com/en/latest/managing/teams/team-notifications.html).
 
-        ```python
-        import pulumi
-        ```
-
         ### TeamEmail
 
         Sends an email to every member of a team.
 
-        ```python
-        import pulumi
-        ```
-
         ### Splunk On-Call (formerly VictorOps)
 
-        ```python
-        import pulumi
-        ```
-
         ### Webhooks
 
         You need to include all the commas even if you only use a credential id.
 
         You can either configure a Webhook to use an existing integration's credential id:
-        ```python
-        import pulumi
-        ```
 
         Or configure one inline:
 
-        ```python
-        import pulumi
-        ```
-
-        ## Arguments
-
-        * `name` - (Required) Name of the SLO. Each SLO name must be unique within an organization.
-        * `description` - (Optional) Description of the SLO.
-        * `type` - (Required) Type of the SLO. Currently just: `"RequestBased"` is supported.
-        * `input` - (Required) Properties to configure an SLO object inputs
-          * `program_text` - (Required) SignalFlow program and arguments text strings that define the streams used as successful event count and total event count
-          * `good_events_label` - (Required) Label used in `"program_text"` that refers to the data block which contains the stream of successful events
-          * `total_events_label` - (Required) Label used in `"program_text"` that refers to the data block which contains the stream of total events
-        * `target` - (Required) Define target value of the service level indicator in the appropriate time period.
-          * `type` - (Required) SLO target type can be the following type: `"RollingWindow"`
-          * `compliance_period` - (Required for `"RollingWindow"` type) Compliance period of this SLO. This value must be within the range of 1d (1 days) to 30d (30 days), inclusive.
-          * `slo` - (Required) Target value in the form of a percentage
-          * `alert_rule` - (Required) List of alert rules you want to set for this SLO target. An SLO alert rule of type BREACH is always required.
-            * `type` - (Required) SLO alert rule can be one of the following types: BREACH, ERROR_BUDGET_LEFT, BURN_RATE. Within an SLO object, you can only specify one SLO alert_rule per type. For example, you can't specify two alert_rule of type BREACH. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-            * `rule` - (Required) Set of rules used for alerting.
-                * `severity` - (Required) The severity of the rule, must be one of: `"Critical"`, `"Major"`, `"Minor"`, `"Warning"`, `"Info"`.
-                * `description` - (Optional) Description for the rule. Displays as the alert condition in the Alert Rules tab of the detector editor in the web UI.
-                * `disabled` - (Optional) When true, notifications and events will not be generated for the detect label. `false` by default.
-                * `notifications` - (Optional) List of strings specifying where notifications will be sent when an incident occurs. See [Create SLO](https://dev.splunk.com/observability/reference/api/slo/latest#endpoint-create-new-slo) for more info.
-                * `parameterized_body` - (Optional) Custom notification message body when an alert is triggered. See [Alert message](https://docs.splunk.com/observability/en/alerts-detectors-notifications/create-detectors-for-alerts.html#alert-messages) for more info.
-                * `parameterized_subject` - (Optional) Custom notification message subject when an alert is triggered. See [Alert message](https://docs.splunk.com/observability/en/alerts-detectors-notifications/create-detectors-for-alerts.html#alert-messages) for more info.
-                * `runbook_url` - (Optional) URL of page to consult when an alert is triggered. This can be used with custom notification messages.
-                * `tip` - (Optional) Plain text suggested first course of action, such as a command line to execute. This can be used with custom notification messages.
-                * `parameters` - (Optional) Parameters for the SLO alert rule. Each SLO alert rule type accepts different parameters. If not specified, default parameters are used.
-                  * `fire_lasting` - (Optional) Duration that indicates how long the alert condition is met before the alert is triggered. The value must be positive and smaller than the compliance period of the SLO target. Note: `"BREACH"` and `"ERROR_BUDGET_LEFT"` alert rules use the fireLasting parameter. Default: `"5m"`
-                  * `percent_of_lasting` - (Optional) Percentage of the `"fire_lasting"` duration that the alert condition is met before the alert is triggered. Note: `"BREACH"` and `"ERROR_BUDGET_LEFT"` alert rules use the `"percent_of_lasting"` parameter. Default: `100`
-                  * `percent_error_budget_left` - (Optional) Error budget must be equal to or smaller than this percentage for the alert to be triggered. Note: `"ERROR_BUDGET_LEFT"` alert rules use the `"percent_error_budget_left"` parameter. Default: `100`
-                  * `short_window_1` - (Optional) Short window 1 used in burn rate alert calculation. This value must be longer than 1/30 of `"long_window_1"`. Note: `"BURN_RATE"` alert rules use the `"short_window_1"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-                  * `short_window_2` - (Optional) Short window 2 used in burn rate alert calculation. This value must be longer than 1/30 of `"long_window_2"`. Note: `"BURN_RATE"` alert rules use the `"short_window_2"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-                  * `long_window_1` - (Optional) Long window 1 used in burn rate alert calculation. This value must be longer than `"short_window_1"` and shorter than 90 days. Note: `"BURN_RATE"` alert rules use the `"long_window_1"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-                  * `long_window_2` - (Optional) Long window 2 used in burn rate alert calculation. This value must be longer than `"short_window_2"` and shorter than 90 days. Note: `"BURN_RATE"` alert rules use the `"long_window_2"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-                  * `burn_rate_threshold_1` - (Optional) Burn rate threshold 1 used in burn rate alert calculation. This value must be between 0 and 100/(100-SLO target). Note: `"BURN_RATE"` alert rules use the `"burn_rate_threshold_1"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-                  * `burn_rate_threshold_2` - (Optional) Burn rate threshold 2 used in burn rate alert calculation. This value must be between 0 and 100/(100-SLO target). Note: `"BURN_RATE"` alert rules use the `"burn_rate_threshold_2"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-
         :param str resource_name: The name of the resource.
         :param pulumi.ResourceOptions opts: Options for the resource.
-        :param pulumi.Input[str] description: Description of the SLO
-        :param pulumi.Input[pulumi.InputType['SloInputArgs']] input: SignalFlow program and arguments text strings that define the streams used as successful event count and total event
-               count
-        :param pulumi.Input[str] name: Name of the SLO
-        :param pulumi.Input[pulumi.InputType['SloTargetArgs']] target: Define target value of the service level indicator in the appropriate time period.
-        :param pulumi.Input[str] type: Type of the SLO. Currently only RequestBased SLO is supported
+        :param pulumi.Input[str] description: Description of the SLO.
+        :param pulumi.Input[Union['SloInputArgs', 'SloInputArgsDict']] input: Properties to configure an SLO object inputs
+        :param pulumi.Input[str] name: Name of the SLO. Each SLO name must be unique within an organization.
+        :param pulumi.Input[Union['SloTargetArgs', 'SloTargetArgsDict']] target: Define target value of the service level indicator in the appropriate time period.
+        :param pulumi.Input[str] type: Type of the SLO. Currently just: `"RequestBased"` is supported.
         """
         ...
     @overload
@@ -346,126 +298,78 @@ class Slo(pulumi.CustomResource):
 
         To learn more about this feature take a look on [documentation for SLO](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/slo-intro.html).
 
-        ## Notification format
-
-        As Splunk Observability Cloud supports different notification mechanisms, use a comma-delimited string to provide inputs. If you want to specify multiple notifications, each must be a member in the list, like so:
+        ## Example
 
         ```python
         import pulumi
+        import pulumi_signalfx as signalfx
+
+        foo_service_slo = signalfx.Slo("foo_service_slo",
+            name="foo service SLO",
+            type="RequestBased",
+            description="SLO monitoring for foo service",
+            input={
+                "program_text": \"\"\"G = data('spans.count', filter=filter('sf_error', 'false') and filter('sf_service', 'foo-service'))
+        T = data('spans.count', filter=filter('sf_service', 'foo-service'))\"\"\",
+                "good_events_label": "G",
+                "total_events_label": "T",
+            },
+            target={
+                "type": "RollingWindow",
+                "slo": 95,
+                "compliance_period": "30d",
+                "alert_rules": [{
+                    "type": "BREACH",
+                    "rules": [{
+                        "severity": "Warning",
+                        "notifications": ["Email,foo-alerts@bar.com"],
+                    }],
+                }],
+            })
         ```
 
+        ## Notification format
+
+        As Splunk Observability Cloud supports different notification mechanisms, use a comma-delimited string to provide inputs. If you want to specify multiple notifications, each must be a member in the list, like so:
+
         See [Splunk Observability Cloud Docs](https://dev.splunk.com/observability/reference/api/detectors/latest) for more information.
 
         Here are some example of how to configure each notification type:
 
         ### Email
 
-        ```python
-        import pulumi
-        ```
-
         ### Jira
 
         Note that the `credentialId` is the Splunk-provided ID shown after setting up your Jira integration. See also `jira.Integration`.
 
-        ```python
-        import pulumi
-        ```
-
         ### OpsGenie
 
         Note that the `credentialId` is the Splunk-provided ID shown after setting up your Opsgenie integration. `Team` here is hardcoded as the `responderType` as that is the only acceptable type as per the API docs.
 
-        ```python
-        import pulumi
-        ```
-
         ### PagerDuty
 
-        ```python
-        import pulumi
-        ```
-
         ### Slack
 
         Exclude the `#` on the channel name:
 
-        ```python
-        import pulumi
-        ```
-
         ### Team
 
         Sends [notifications to a team](https://docs.signalfx.com/en/latest/managing/teams/team-notifications.html).
 
-        ```python
-        import pulumi
-        ```
-
         ### TeamEmail
 
         Sends an email to every member of a team.
 
-        ```python
-        import pulumi
-        ```
-
         ### Splunk On-Call (formerly VictorOps)
 
-        ```python
-        import pulumi
-        ```
-
         ### Webhooks
 
         You need to include all the commas even if you only use a credential id.
 
         You can either configure a Webhook to use an existing integration's credential id:
-        ```python
-        import pulumi
-        ```
 
         Or configure one inline:
 
-        ```python
-        import pulumi
-        ```
-
-        ## Arguments
-
-        * `name` - (Required) Name of the SLO. Each SLO name must be unique within an organization.
-        * `description` - (Optional) Description of the SLO.
-        * `type` - (Required) Type of the SLO. Currently just: `"RequestBased"` is supported.
-        * `input` - (Required) Properties to configure an SLO object inputs
-          * `program_text` - (Required) SignalFlow program and arguments text strings that define the streams used as successful event count and total event count
-          * `good_events_label` - (Required) Label used in `"program_text"` that refers to the data block which contains the stream of successful events
-          * `total_events_label` - (Required) Label used in `"program_text"` that refers to the data block which contains the stream of total events
-        * `target` - (Required) Define target value of the service level indicator in the appropriate time period.
-          * `type` - (Required) SLO target type can be the following type: `"RollingWindow"`
-          * `compliance_period` - (Required for `"RollingWindow"` type) Compliance period of this SLO. This value must be within the range of 1d (1 days) to 30d (30 days), inclusive.
-          * `slo` - (Required) Target value in the form of a percentage
-          * `alert_rule` - (Required) List of alert rules you want to set for this SLO target. An SLO alert rule of type BREACH is always required.
-            * `type` - (Required) SLO alert rule can be one of the following types: BREACH, ERROR_BUDGET_LEFT, BURN_RATE. Within an SLO object, you can only specify one SLO alert_rule per type. For example, you can't specify two alert_rule of type BREACH. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-            * `rule` - (Required) Set of rules used for alerting.
-                * `severity` - (Required) The severity of the rule, must be one of: `"Critical"`, `"Major"`, `"Minor"`, `"Warning"`, `"Info"`.
-                * `description` - (Optional) Description for the rule. Displays as the alert condition in the Alert Rules tab of the detector editor in the web UI.
-                * `disabled` - (Optional) When true, notifications and events will not be generated for the detect label. `false` by default.
-                * `notifications` - (Optional) List of strings specifying where notifications will be sent when an incident occurs. See [Create SLO](https://dev.splunk.com/observability/reference/api/slo/latest#endpoint-create-new-slo) for more info.
-                * `parameterized_body` - (Optional) Custom notification message body when an alert is triggered. See [Alert message](https://docs.splunk.com/observability/en/alerts-detectors-notifications/create-detectors-for-alerts.html#alert-messages) for more info.
-                * `parameterized_subject` - (Optional) Custom notification message subject when an alert is triggered. See [Alert message](https://docs.splunk.com/observability/en/alerts-detectors-notifications/create-detectors-for-alerts.html#alert-messages) for more info.
-                * `runbook_url` - (Optional) URL of page to consult when an alert is triggered. This can be used with custom notification messages.
-                * `tip` - (Optional) Plain text suggested first course of action, such as a command line to execute. This can be used with custom notification messages.
-                * `parameters` - (Optional) Parameters for the SLO alert rule. Each SLO alert rule type accepts different parameters. If not specified, default parameters are used.
-                  * `fire_lasting` - (Optional) Duration that indicates how long the alert condition is met before the alert is triggered. The value must be positive and smaller than the compliance period of the SLO target. Note: `"BREACH"` and `"ERROR_BUDGET_LEFT"` alert rules use the fireLasting parameter. Default: `"5m"`
-                  * `percent_of_lasting` - (Optional) Percentage of the `"fire_lasting"` duration that the alert condition is met before the alert is triggered. Note: `"BREACH"` and `"ERROR_BUDGET_LEFT"` alert rules use the `"percent_of_lasting"` parameter. Default: `100`
-                  * `percent_error_budget_left` - (Optional) Error budget must be equal to or smaller than this percentage for the alert to be triggered. Note: `"ERROR_BUDGET_LEFT"` alert rules use the `"percent_error_budget_left"` parameter. Default: `100`
-                  * `short_window_1` - (Optional) Short window 1 used in burn rate alert calculation. This value must be longer than 1/30 of `"long_window_1"`. Note: `"BURN_RATE"` alert rules use the `"short_window_1"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-                  * `short_window_2` - (Optional) Short window 2 used in burn rate alert calculation. This value must be longer than 1/30 of `"long_window_2"`. Note: `"BURN_RATE"` alert rules use the `"short_window_2"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-                  * `long_window_1` - (Optional) Long window 1 used in burn rate alert calculation. This value must be longer than `"short_window_1"` and shorter than 90 days. Note: `"BURN_RATE"` alert rules use the `"long_window_1"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-                  * `long_window_2` - (Optional) Long window 2 used in burn rate alert calculation. This value must be longer than `"short_window_2"` and shorter than 90 days. Note: `"BURN_RATE"` alert rules use the `"long_window_2"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-                  * `burn_rate_threshold_1` - (Optional) Burn rate threshold 1 used in burn rate alert calculation. This value must be between 0 and 100/(100-SLO target). Note: `"BURN_RATE"` alert rules use the `"burn_rate_threshold_1"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-                  * `burn_rate_threshold_2` - (Optional) Burn rate threshold 2 used in burn rate alert calculation. This value must be between 0 and 100/(100-SLO target). Note: `"BURN_RATE"` alert rules use the `"burn_rate_threshold_2"` parameter. See [SLO alerts](https://docs.splunk.com/observability/en/alerts-detectors-notifications/slo/burn-rate-alerts.html) for more info.
-
         :param str resource_name: The name of the resource.
         :param SloArgs args: The arguments to use to populate this resource's properties.
         :param pulumi.ResourceOptions opts: Options for the resource.
@@ -482,9 +386,9 @@ class Slo(pulumi.CustomResource):
                  resource_name: str,
                  opts: Optional[pulumi.ResourceOptions] = None,
                  description: Optional[pulumi.Input[str]] = None,
-                 input: Optional[pulumi.Input[pulumi.InputType['SloInputArgs']]] = None,
+                 input: Optional[pulumi.Input[Union['SloInputArgs', 'SloInputArgsDict']]] = None,
                  name: Optional[pulumi.Input[str]] = None,
-                 target: Optional[pulumi.Input[pulumi.InputType['SloTargetArgs']]] = None,
+                 target: Optional[pulumi.Input[Union['SloTargetArgs', 'SloTargetArgsDict']]] = None,
                  type: Optional[pulumi.Input[str]] = None,
                  __props__=None):
         opts = pulumi.ResourceOptions.merge(_utilities.get_resource_opts_defaults(), opts)
@@ -517,9 +421,9 @@ class Slo(pulumi.CustomResource):
             id: pulumi.Input[str],
             opts: Optional[pulumi.ResourceOptions] = None,
             description: Optional[pulumi.Input[str]] = None,
-            input: Optional[pulumi.Input[pulumi.InputType['SloInputArgs']]] = None,
+            input: Optional[pulumi.Input[Union['SloInputArgs', 'SloInputArgsDict']]] = None,
             name: Optional[pulumi.Input[str]] = None,
-            target: Optional[pulumi.Input[pulumi.InputType['SloTargetArgs']]] = None,
+            target: Optional[pulumi.Input[Union['SloTargetArgs', 'SloTargetArgsDict']]] = None,
             type: Optional[pulumi.Input[str]] = None) -> 'Slo':
         """
         Get an existing Slo resource's state with the given name, id, and optional extra
@@ -528,12 +432,11 @@ class Slo(pulumi.CustomResource):
         :param str resource_name: The unique name of the resulting resource.
         :param pulumi.Input[str] id: The unique provider ID of the resource to lookup.
         :param pulumi.ResourceOptions opts: Options for the resource.
-        :param pulumi.Input[str] description: Description of the SLO
-        :param pulumi.Input[pulumi.InputType['SloInputArgs']] input: SignalFlow program and arguments text strings that define the streams used as successful event count and total event
-               count
-        :param pulumi.Input[str] name: Name of the SLO
-        :param pulumi.Input[pulumi.InputType['SloTargetArgs']] target: Define target value of the service level indicator in the appropriate time period.
-        :param pulumi.Input[str] type: Type of the SLO. Currently only RequestBased SLO is supported
+        :param pulumi.Input[str] description: Description of the SLO.
+        :param pulumi.Input[Union['SloInputArgs', 'SloInputArgsDict']] input: Properties to configure an SLO object inputs
+        :param pulumi.Input[str] name: Name of the SLO. Each SLO name must be unique within an organization.
+        :param pulumi.Input[Union['SloTargetArgs', 'SloTargetArgsDict']] target: Define target value of the service level indicator in the appropriate time period.
+        :param pulumi.Input[str] type: Type of the SLO. Currently just: `"RequestBased"` is supported.
         """
         opts = pulumi.ResourceOptions.merge(opts, pulumi.ResourceOptions(id=id))
 
@@ -550,7 +453,7 @@ class Slo(pulumi.CustomResource):
     @pulumi.getter
     def description(self) -> pulumi.Output[Optional[str]]:
         """
-        Description of the SLO
+        Description of the SLO.
         """
         return pulumi.get(self, "description")
 
@@ -558,8 +461,7 @@ class Slo(pulumi.CustomResource):
     @pulumi.getter
     def input(self) -> pulumi.Output['outputs.SloInput']:
         """
-        SignalFlow program and arguments text strings that define the streams used as successful event count and total event
-        count
+        Properties to configure an SLO object inputs
         """
         return pulumi.get(self, "input")
 
@@ -567,7 +469,7 @@ class Slo(pulumi.CustomResource):
     @pulumi.getter
     def name(self) -> pulumi.Output[str]:
         """
-        Name of the SLO
+        Name of the SLO. Each SLO name must be unique within an organization.
         """
         return pulumi.get(self, "name")
 
@@ -583,7 +485,7 @@ class Slo(pulumi.CustomResource):
     @pulumi.getter
     def type(self) -> pulumi.Output[str]:
         """
-        Type of the SLO. Currently only RequestBased SLO is supported
+        Type of the SLO. Currently just: `"RequestBased"` is supported.
         """
         return pulumi.get(self, "type")