Class EnableCostAnomalyMonitorRequest
Implements
Inherited Members
Namespace: Oci.BudgetService.Requests
Assembly: OCI.DotNetSDK.Budget.dll
Syntax
public class EnableCostAnomalyMonitorRequest : IOciRequest
Examples
Click here to see an example of how to use EnableCostAnomalyMonitor request.
Properties
CostAnomalyMonitorId
Declaration
[Required(ErrorMessage = "CostAnomalyMonitorId is required.")]
[HttpConverter(TargetEnum.Path, "costAnomalyMonitorId")]
public string CostAnomalyMonitorId { get; set; }
Property Value
| Type | Description |
|---|---|
| string | The unique costAnomalyMonitor OCID. |
Remarks
Required
IfMatch
Declaration
[HttpConverter(TargetEnum.Header, "if-match")]
public string IfMatch { get; set; }
Property Value
| Type | Description |
|---|---|
| string | For optimistic concurrency control. In the PUT or DELETE call
for a resource, set the |
OpcRequestId
Declaration
[HttpConverter(TargetEnum.Header, "opc-request-id")]
public string OpcRequestId { get; set; }
Property Value
| Type | Description |
|---|---|
| string | The client request ID for tracing. |
OpcRetryToken
Declaration
[HttpConverter(TargetEnum.Header, "opc-retry-token")]
public string OpcRetryToken { get; set; }
Property Value
| Type | Description |
|---|---|
| string | A token that uniquely identifies a request so it can be retried, in case of a timeout or server error, without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected. |