/AWS1/CL_CEX=>UPDATEANOMALYSUBSCRIPTION()
¶
About UpdateAnomalySubscription¶
Updates an existing cost anomaly subscription. Specify the fields that you want to update. Omitted fields are unchanged.
The JSON below describes the generic construct for each type. See Request Parameters for possible values as they apply to
AnomalySubscription
.
Method Signature¶
IMPORTING¶
Required arguments:¶
IV_SUBSCRIPTIONARN
TYPE /AWS1/CEXGENERICSTRING
/AWS1/CEXGENERICSTRING
¶
A cost anomaly subscription Amazon Resource Name (ARN).
Optional arguments:¶
IV_THRESHOLD
TYPE /AWS1/RT_DOUBLE_AS_STRING
/AWS1/RT_DOUBLE_AS_STRING
¶
(deprecated)
The update to the threshold value for receiving notifications.
This field has been deprecated. To update a threshold, use ThresholdExpression. Continued use of Threshold will be treated as shorthand syntax for a ThresholdExpression.
You can specify either Threshold or ThresholdExpression, but not both.
IV_FREQUENCY
TYPE /AWS1/CEXANOMALYSUBSCRIPTION00
/AWS1/CEXANOMALYSUBSCRIPTION00
¶
The update to the frequency value that subscribers receive notifications.
IT_MONITORARNLIST
TYPE /AWS1/CL_CEXMONITORARNLIST_W=>TT_MONITORARNLIST
TT_MONITORARNLIST
¶
A list of cost anomaly monitor ARNs.
IT_SUBSCRIBERS
TYPE /AWS1/CL_CEXSUBSCRIBER=>TT_SUBSCRIBERS
TT_SUBSCRIBERS
¶
The update to the subscriber list.
IV_SUBSCRIPTIONNAME
TYPE /AWS1/CEXGENERICSTRING
/AWS1/CEXGENERICSTRING
¶
The new name of the subscription.
IO_THRESHOLDEXPRESSION
TYPE REF TO /AWS1/CL_CEXEXPRESSION
/AWS1/CL_CEXEXPRESSION
¶
The update to the Expression object used to specify the anomalies that you want to generate alerts for. This supports dimensions and nested expressions. The supported dimensions are
ANOMALY_TOTAL_IMPACT_ABSOLUTE
andANOMALY_TOTAL_IMPACT_PERCENTAGE
, corresponding to an anomaly’s TotalImpact and TotalImpactPercentage, respectively (see Impact for more details). The supported nested expression types areAND
andOR
. The match optionGREATER_THAN_OR_EQUAL
is required. Values must be numbers between 0 and 10,000,000,000 in string format.You can specify either Threshold or ThresholdExpression, but not both.
The following are examples of valid ThresholdExpressions:
Absolute threshold:
{ "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }
Percentage threshold:
{ "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }
AND
two thresholds together:{ "And": [ { "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, { "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } } ] }
OR
two thresholds together:{ "Or": [ { "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, { "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } } ] }