AnomalyMonitor
This object continuously inspects your account's cost data for anomalies. It's based
on MonitorType
and MonitorSpecification
. The content consists
of detailed metadata and the current status of the monitor object.
Contents
- MonitorName
-
The name of the monitor.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 1024.
Pattern:
[\S\s]*
Required: Yes
- MonitorType
-
The possible type values.
Type: String
Valid Values:
DIMENSIONAL | CUSTOM
Required: Yes
- CreationDate
-
The date when the monitor was created.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 40.
Pattern:
(\d{4}-\d{2}-\d{2})(T\d{2}:\d{2}:\d{2}Z)?
Required: No
- DimensionalValueCount
-
The value for evaluated dimensions.
Type: Integer
Valid Range: Minimum value of 0.
Required: No
- LastEvaluatedDate
-
The date when the monitor last evaluated for anomalies.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 40.
Pattern:
(\d{4}-\d{2}-\d{2})(T\d{2}:\d{2}:\d{2}Z)?
Required: No
- LastUpdatedDate
-
The date when the monitor was last updated.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 40.
Pattern:
(\d{4}-\d{2}-\d{2})(T\d{2}:\d{2}:\d{2}Z)?
Required: No
- MonitorArn
-
The Amazon Resource Name (ARN) value.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 1024.
Pattern:
[\S\s]*
Required: No
- MonitorDimension
-
The dimensions to evaluate.
Type: String
Valid Values:
SERVICE
Required: No
- MonitorSpecification
-
Use
Expression
to filter in various Cost Explorer APIs.Not all
Expression
types are supported in each API. Refer to the documentation for each specific API to see what is supported.There are two patterns:
-
Simple dimension values.
-
There are three types of simple dimension values:
CostCategories
,Tags
, andDimensions
.-
Specify the
CostCategories
field to define a filter that acts on Cost Categories. -
Specify the
Tags
field to define a filter that acts on Cost Allocation Tags. -
Specify the
Dimensions
field to define a filter that acts on theDimensionValues
.
-
-
For each filter type, you can set the dimension name and values for the filters that you plan to use.
-
For example, you can filter for
REGION==us-east-1 OR REGION==us-west-1
. ForGetRightsizingRecommendation
, the Region is a full name (for example,REGION==US East (N. Virginia)
. -
The corresponding
Expression
for this example is as follows:{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1", "us-west-1" ] } }
-
As shown in the previous example, lists of dimension values are combined with
OR
when applying the filter.
-
-
You can also set different match options to further control how the filter behaves. Not all APIs support match options. Refer to the documentation for each specific API to see what is supported.
-
For example, you can filter for linked account names that start with "a".
-
The corresponding
Expression
for this example is as follows:{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }
-
-
-
Compound
Expression
types with logical operations.-
You can use multiple
Expression
types and the logical operatorsAND/OR/NOT
to create a list of one or moreExpression
objects. By doing this, you can filter by more advanced options. -
For example, you can filter by
((REGION == us-east-1 OR REGION == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE != DataTransfer)
. -
The corresponding
Expression
for this example is as follows:{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName", "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key": "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] }
Note
Because each
Expression
can have only one operator, the service returns an error if more than one is specified. The following example shows anExpression
object that creates an error:{ "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [ "DataTransfer" ] } }
The following is an example of the corresponding error message:
"Expression has more than one roots. Only one root operator is allowed for each expression: And, Or, Not, Dimensions, Tags, CostCategories"
-
Note
For the
GetRightsizingRecommendation
action, a combination of OR and NOT isn't supported. OR isn't supported between different dimensions, or dimensions and tags. NOT operators aren't supported. Dimensions are also limited toLINKED_ACCOUNT
,REGION
, orRIGHTSIZING_TYPE
.For the
GetReservationPurchaseRecommendation
action, only NOT is supported. AND and OR aren't supported. Dimensions are limited toLINKED_ACCOUNT
.Type: Expression object
Required: No
-
See Also
For more information about using this API in one of the language-specific Amazon SDKs, see the following: