class Aws::CostExplorer::Types::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.

@note When making an API call, you may pass AnomalyMonitor

data as a hash:

    {
      monitor_arn: "GenericString",
      monitor_name: "GenericString", # required
      creation_date: "YearMonthDay",
      last_updated_date: "YearMonthDay",
      last_evaluated_date: "YearMonthDay",
      monitor_type: "DIMENSIONAL", # required, accepts DIMENSIONAL, CUSTOM
      monitor_dimension: "SERVICE", # accepts SERVICE
      monitor_specification: {
        or: [
          {
            # recursive Expression
          },
        ],
        and: [
          {
            # recursive Expression
          },
        ],
        not: {
          # recursive Expression
        },
        dimensions: {
          key: "AZ", # accepts AZ, INSTANCE_TYPE, LINKED_ACCOUNT, LINKED_ACCOUNT_NAME, OPERATION, PURCHASE_TYPE, REGION, SERVICE, SERVICE_CODE, USAGE_TYPE, USAGE_TYPE_GROUP, RECORD_TYPE, OPERATING_SYSTEM, TENANCY, SCOPE, PLATFORM, SUBSCRIPTION_ID, LEGAL_ENTITY_NAME, DEPLOYMENT_OPTION, DATABASE_ENGINE, CACHE_ENGINE, INSTANCE_TYPE_FAMILY, BILLING_ENTITY, RESERVATION_ID, RESOURCE_ID, RIGHTSIZING_TYPE, SAVINGS_PLANS_TYPE, SAVINGS_PLAN_ARN, PAYMENT_OPTION, AGREEMENT_END_DATE_TIME_AFTER, AGREEMENT_END_DATE_TIME_BEFORE
          values: ["Value"],
          match_options: ["EQUALS"], # accepts EQUALS, ABSENT, STARTS_WITH, ENDS_WITH, CONTAINS, CASE_SENSITIVE, CASE_INSENSITIVE
        },
        tags: {
          key: "TagKey",
          values: ["Value"],
          match_options: ["EQUALS"], # accepts EQUALS, ABSENT, STARTS_WITH, ENDS_WITH, CONTAINS, CASE_SENSITIVE, CASE_INSENSITIVE
        },
        cost_categories: {
          key: "CostCategoryName",
          values: ["Value"],
          match_options: ["EQUALS"], # accepts EQUALS, ABSENT, STARTS_WITH, ENDS_WITH, CONTAINS, CASE_SENSITIVE, CASE_INSENSITIVE
        },
      },
      dimensional_value_count: 1,
    }

@!attribute [rw] monitor_arn

The Amazon Resource Name (ARN) value.
@return [String]

@!attribute [rw] monitor_name

The name of the monitor.
@return [String]

@!attribute [rw] creation_date

The date when the monitor was created.
@return [String]

@!attribute [rw] last_updated_date

The date when the monitor was last updated.
@return [String]

@!attribute [rw] last_evaluated_date

The date when the monitor last evaluated for anomalies.
@return [String]

@!attribute [rw] monitor_type

The possible type values.
@return [String]

@!attribute [rw] monitor_dimension

The dimensions to evaluate.
@return [String]

@!attribute [rw] monitor_specification

Use `Expression` to filter by cost or by usage. There are two
patterns:

* Simple dimension values - 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`. For
  `GetRightsizingRecommendation`, the Region is a full name (for
  example, `REGION==US East (N. Virginia)`. The `Expression` example
  is as follows:

  `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
  “us-west-1” ] \} \}`

  The list of dimension values are OR'd together to retrieve cost
  or usage data. You can create `Expression` and `DimensionValues`
  objects using either `with*` methods or `set*` methods in multiple
  lines.

* Compound dimension values with logical operations - You can use
  multiple `Expression` types and the logical operators `AND/OR/NOT`
  to create a list of one or more `Expression` objects. By doing
  this, you can filter on more advanced options. For example, you
  can filter on `((REGION == us-east-1 OR REGION == us-west-1) OR
  (TAG.Type == Type1)) AND (USAGE_TYPE != DataTransfer)`. The
  `Expression` for that 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 markdown="1"> Because each `Expression` can have only one operator, the service
  returns an error if more than one is specified. The following
  example shows an `Expression` object that creates an error.

   </note>

  ` \{ "And": [ ... ], "DimensionValues": \{ "Dimension":
  "USAGE_TYPE", "Values": [ "DataTransfer" ] \} \} `

<note markdown="1"> 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 to `LINKED_ACCOUNT`, `REGION`, or
`RIGHTSIZING_TYPE`.

 For the `GetReservationPurchaseRecommendation` action, only NOT is
supported. AND and OR aren't supported. Dimensions are limited to
`LINKED_ACCOUNT`.

 </note>
@return [Types::Expression]

@!attribute [rw] dimensional_value_count

The value for evaluated dimensions.
@return [Integer]

@see docs.aws.amazon.com/goto/WebAPI/ce-2017-10-25/AnomalyMonitor AWS API Documentation

Constants

SENSITIVE