/AWS1/CL_CEXCOSTCOMPARISONDR00¶
Represents a collection of cost drivers and their associated metrics for cost comparison analysis.
CONSTRUCTOR¶
IMPORTING¶
Optional arguments:¶
io_costselector TYPE REF TO /AWS1/CL_CEXEXPRESSION /AWS1/CL_CEXEXPRESSION¶
Use
Expressionto filter in various Cost Explorer APIs.Not all
Expressiontypes 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
CostCategoriesfield to define a filter that acts on Cost Categories.Specify the
Tagsfield to define a filter that acts on Cost Allocation Tags.Specify the
Dimensionsfield 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
Expressionfor 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
ORwhen 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
Expressionfor this example is as follows:{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }Compound
Expressiontypes with logical operations.
You can use multiple
Expressiontypes and the logical operatorsAND/OR/NOTto create a list of one or moreExpressionobjects. 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
Expressionfor 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"] }}} ] }Because each
Expressioncan have only one operator, the service returns an error if more than one is specified. The following example shows anExpressionobject 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"For the
GetRightsizingRecommendationaction, 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
GetReservationPurchaseRecommendationaction, only NOT is supported. AND and OR aren't supported. Dimensions are limited toLINKED_ACCOUNT.
it_metrics TYPE /AWS1/CL_CEXCOMPARISONMETRIC00=>TT_COMPARISONMETRICS TT_COMPARISONMETRICS¶
A mapping of metric names to their comparison values.
it_costdrivers TYPE /AWS1/CL_CEXCOSTDRIVER=>TT_COSTDRIVERS TT_COSTDRIVERS¶
An array of cost drivers, each representing a cost difference between the baseline and comparison time periods. Each entry also includes a metric delta (for example, usage change) that contributed to the cost variance, along with the identifier and type of change.
Queryable Attributes¶
CostSelector¶
Use
Expressionto filter in various Cost Explorer APIs.Not all
Expressiontypes 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
CostCategoriesfield to define a filter that acts on Cost Categories.Specify the
Tagsfield to define a filter that acts on Cost Allocation Tags.Specify the
Dimensionsfield 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
Expressionfor 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
ORwhen 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
Expressionfor this example is as follows:{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }Compound
Expressiontypes with logical operations.
You can use multiple
Expressiontypes and the logical operatorsAND/OR/NOTto create a list of one or moreExpressionobjects. 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
Expressionfor 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"] }}} ] }Because each
Expressioncan have only one operator, the service returns an error if more than one is specified. The following example shows anExpressionobject 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"For the
GetRightsizingRecommendationaction, 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
GetReservationPurchaseRecommendationaction, only NOT is supported. AND and OR aren't supported. Dimensions are limited toLINKED_ACCOUNT.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_COSTSELECTOR() |
Getter for COSTSELECTOR |
Metrics¶
A mapping of metric names to their comparison values.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_METRICS() |
Getter for METRICS, with configurable default |
ASK_METRICS() |
Getter for METRICS w/ exceptions if field has no value |
HAS_METRICS() |
Determine if METRICS has a value |
CostDrivers¶
An array of cost drivers, each representing a cost difference between the baseline and comparison time periods. Each entry also includes a metric delta (for example, usage change) that contributed to the cost variance, along with the identifier and type of change.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_COSTDRIVERS() |
Getter for COSTDRIVERS, with configurable default |
ASK_COSTDRIVERS() |
Getter for COSTDRIVERS w/ exceptions if field has no value |
HAS_COSTDRIVERS() |
Determine if COSTDRIVERS has a value |
Public Local Types In This Class¶
Internal table types, representing arrays and maps of this class, are defined as local types:
TT_COSTCOMPARISONDRIVERS¶
TYPES TT_COSTCOMPARISONDRIVERS TYPE STANDARD TABLE OF REF TO /AWS1/CL_CEXCOSTCOMPARISONDR00 WITH DEFAULT KEY
.