pulumi-oci 1.40.0a1718172898__py3-none-any.whl → 1.40.0a1718211931__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (10) hide show
  1. pulumi_oci/loganalytics/namespace.py +2 -2
  2. pulumi_oci/monitoring/_inputs.py +10 -6
  3. pulumi_oci/monitoring/alarm.py +189 -28
  4. pulumi_oci/monitoring/get_alarm.py +44 -5
  5. pulumi_oci/monitoring/outputs.py +87 -28
  6. pulumi_oci/pulumi-plugin.json +1 -1
  7. {pulumi_oci-1.40.0a1718172898.dist-info → pulumi_oci-1.40.0a1718211931.dist-info}/METADATA +1 -1
  8. {pulumi_oci-1.40.0a1718172898.dist-info → pulumi_oci-1.40.0a1718211931.dist-info}/RECORD +10 -10
  9. {pulumi_oci-1.40.0a1718172898.dist-info → pulumi_oci-1.40.0a1718211931.dist-info}/WHEEL +0 -0
  10. {pulumi_oci-1.40.0a1718172898.dist-info → pulumi_oci-1.40.0a1718211931.dist-info}/top_level.txt +0 -0
pulumi_oci/loganalytics/namespace.py CHANGED
@@ -151,7 +151,7 @@ class Namespace(pulumi.CustomResource):
151
151
  Namespace can be imported using the `compartment_id` and `namespace`, e.g.
152
152
 
153
153
  ```sh
154
- $ pulumi import oci:LogAnalytics/namespace:Namespace test_namespace "compartmentId/<compartment_id>/namespace/<namespace>"
154
+ $ pulumi import oci:LogAnalytics/namespace:Namespace test_namespace "compartmentId/{compartment_id}/namespace/{namespace}"
155
155
  ```
156
156
 
157
157
  :param str resource_name: The name of the resource.
@@ -188,7 +188,7 @@ class Namespace(pulumi.CustomResource):
188
188
  Namespace can be imported using the `compartment_id` and `namespace`, e.g.
189
189
 
190
190
  ```sh
191
- $ pulumi import oci:LogAnalytics/namespace:Namespace test_namespace "compartmentId/<compartment_id>/namespace/<namespace>"
191
+ $ pulumi import oci:LogAnalytics/namespace:Namespace test_namespace "compartmentId/{compartment_id}/namespace/{namespace}"
192
192
  ```
193
193
 
194
194
  :param str resource_name: The name of the resource.
pulumi_oci/monitoring/_inputs.py CHANGED
@@ -29,7 +29,7 @@ class AlarmOverrideArgs:
29
29
  rule_name: Optional[pulumi.Input[str]] = None,
30
30
  severity: Optional[pulumi.Input[str]] = None):
31
31
  """
32
- :param pulumi.Input[str] body: (Updatable) The human-readable content of the delivered alarm notification. Oracle recommends providing guidance to operators for resolving the alarm condition. Consider adding links to standard runbook practices. Avoid entering confidential information. Example: `High CPU usage alert. Follow runbook instructions for resolution.`
32
+ :param pulumi.Input[str] body: (Updatable) The human-readable content of the delivered alarm notification. Optionally include [dynamic variables](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Tasks/update-alarm-dynamic-variables.htm). Oracle recommends providing guidance to operators for resolving the alarm condition. Consider adding links to standard runbook practices. Avoid entering confidential information. Example: `High CPU usage alert. Follow runbook instructions for resolution.`
33
33
  :param pulumi.Input[str] pending_duration: (Updatable) The period of time that the condition defined in the alarm must persist before the alarm state changes from "OK" to "FIRING". For example, a value of 5 minutes means that the alarm must persist in breaching the condition for five minutes before the alarm updates its state to "FIRING".
34
34
 
35
35
  The duration is specified as a string in ISO 8601 format (`PT10M` for ten minutes or `PT1H` for one hour). Minimum: PT1M. Maximum: PT1H. Default: PT1M.
@@ -39,7 +39,7 @@ class AlarmOverrideArgs:
39
39
  The alarm updates its status to "OK" when the breaching condition has been clear for the most recent minute.
40
40
 
41
41
  Example: `PT5M`
42
- :param pulumi.Input[str] query: (Updatable) The Monitoring Query Language (MQL) expression to evaluate for the alarm. The Alarms feature of the Monitoring service interprets results for each returned time series as Boolean values, where zero represents false and a non-zero value represents true. A true value means that the trigger rule condition has been met. The query must specify a metric, statistic, interval, and trigger rule (threshold or absence). Supported values for interval depend on the specified time range. More interval values are supported for smaller time ranges. You can optionally specify dimensions and grouping functions. Supported grouping functions: `grouping()`, `groupBy()`. For information about writing MQL expressions, see [Editing the MQL Expression for a Query](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Tasks/query-metric-mql.htm). For details about MQL, see [Monitoring Query Language (MQL) Reference](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Reference/mql.htm). For available dimensions, review the metric definition for the supported service. See [Supported Services](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Concepts/monitoringoverview.htm#SupportedServices).
42
+ :param pulumi.Input[str] query: (Updatable) The Monitoring Query Language (MQL) expression to evaluate for the alarm. The Alarms feature of the Monitoring service interprets results for each returned time series as Boolean values, where zero represents false and a non-zero value represents true. A true value means that the trigger rule condition has been met. The query must specify a metric, statistic, interval, and trigger rule (threshold or absence). Supported values for interval depend on the specified time range. More interval values are supported for smaller time ranges. You can optionally specify dimensions and grouping functions. Also, you can customize the [absence detection period](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Tasks/create-edit-alarm-query-absence-detection-period.htm). Supported grouping functions: `grouping()`, `groupBy()`. For information about writing MQL expressions, see [Editing the MQL Expression for a Query](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Tasks/query-metric-mql.htm). For details about MQL, see [Monitoring Query Language (MQL) Reference](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Reference/mql.htm). For available dimensions, review the metric definition for the supported service. See [Supported Services](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Concepts/monitoringoverview.htm#SupportedServices).
43
43
 
44
44
  Example of threshold alarm:
45
45
 
@@ -55,7 +55,9 @@ class AlarmOverrideArgs:
55
55
 
56
56
  CpuUtilization[1m]{availabilityDomain="cumS:PHX-AD-1"}.absent()
57
57
 
58
- -----
58
+ ----- Example of absence alarm with custom absence detection period of 20 hours:
59
+
60
+ ----- CpuUtilization[1m]{availabilityDomain="cumS:PHX-AD-1"}.absent(20h) -----
59
61
  :param pulumi.Input[str] rule_name: (Updatable) A user-friendly description for this alarm override. Must be unique across all `ruleName` values for the alarm.
60
62
  :param pulumi.Input[str] severity: (Updatable) The perceived severity of the alarm with regard to the affected system. Example: `CRITICAL`
61
63
  """
@@ -74,7 +76,7 @@ class AlarmOverrideArgs:
74
76
  @pulumi.getter
75
77
  def body(self) -> Optional[pulumi.Input[str]]:
76
78
  """
77
- (Updatable) The human-readable content of the delivered alarm notification. Oracle recommends providing guidance to operators for resolving the alarm condition. Consider adding links to standard runbook practices. Avoid entering confidential information. Example: `High CPU usage alert. Follow runbook instructions for resolution.`
79
+ (Updatable) The human-readable content of the delivered alarm notification. Optionally include [dynamic variables](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Tasks/update-alarm-dynamic-variables.htm). Oracle recommends providing guidance to operators for resolving the alarm condition. Consider adding links to standard runbook practices. Avoid entering confidential information. Example: `High CPU usage alert. Follow runbook instructions for resolution.`
78
80
  """
79
81
  return pulumi.get(self, "body")
80
82
 
@@ -106,7 +108,7 @@ class AlarmOverrideArgs:
106
108
  @pulumi.getter
107
109
  def query(self) -> Optional[pulumi.Input[str]]:
108
110
  """
109
- (Updatable) The Monitoring Query Language (MQL) expression to evaluate for the alarm. The Alarms feature of the Monitoring service interprets results for each returned time series as Boolean values, where zero represents false and a non-zero value represents true. A true value means that the trigger rule condition has been met. The query must specify a metric, statistic, interval, and trigger rule (threshold or absence). Supported values for interval depend on the specified time range. More interval values are supported for smaller time ranges. You can optionally specify dimensions and grouping functions. Supported grouping functions: `grouping()`, `groupBy()`. For information about writing MQL expressions, see [Editing the MQL Expression for a Query](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Tasks/query-metric-mql.htm). For details about MQL, see [Monitoring Query Language (MQL) Reference](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Reference/mql.htm). For available dimensions, review the metric definition for the supported service. See [Supported Services](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Concepts/monitoringoverview.htm#SupportedServices).
111
+ (Updatable) The Monitoring Query Language (MQL) expression to evaluate for the alarm. The Alarms feature of the Monitoring service interprets results for each returned time series as Boolean values, where zero represents false and a non-zero value represents true. A true value means that the trigger rule condition has been met. The query must specify a metric, statistic, interval, and trigger rule (threshold or absence). Supported values for interval depend on the specified time range. More interval values are supported for smaller time ranges. You can optionally specify dimensions and grouping functions. Also, you can customize the [absence detection period](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Tasks/create-edit-alarm-query-absence-detection-period.htm). Supported grouping functions: `grouping()`, `groupBy()`. For information about writing MQL expressions, see [Editing the MQL Expression for a Query](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Tasks/query-metric-mql.htm). For details about MQL, see [Monitoring Query Language (MQL) Reference](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Reference/mql.htm). For available dimensions, review the metric definition for the supported service. See [Supported Services](https://docs.cloud.oracle.com/iaas/Content/Monitoring/Concepts/monitoringoverview.htm#SupportedServices).
110
112
 
111
113
  Example of threshold alarm:
112
114
 
@@ -122,7 +124,9 @@ class AlarmOverrideArgs:
122
124
 
123
125
  CpuUtilization[1m]{availabilityDomain="cumS:PHX-AD-1"}.absent()
124
126
 
125
- -----
127
+ ----- Example of absence alarm with custom absence detection period of 20 hours:
128
+
129
+ ----- CpuUtilization[1m]{availabilityDomain="cumS:PHX-AD-1"}.absent(20h) -----
126
130
  """
127
131
  return pulumi.get(self, "query")
128
132