Module aws_sdk_cloudwatchlogs::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that Amazon CloudWatch Logs can respond with.

Structs

• AccountPolicy

  A structure that contains information about one CloudWatch Logs account policy.

• Anomaly

  This structure represents one anomaly that has been found by a logs anomaly detector.

• AnomalyDetector

  Contains information about one anomaly detector in the account.

• Delivery

  This structure contains information about one delivery in your account.

• DeliveryDestination

  This structure contains information about one delivery destination in your account. A delivery destination is an Amazon Web Services resource that represents an Amazon Web Services service that logs can be sent to. CloudWatch Logs, Amazon S3, are supported as Firehose delivery destinations.

• DeliveryDestinationConfiguration

  A structure that contains information about one logs delivery destination.

• DeliverySource

  This structure contains information about one delivery source in your account. A delivery source is an Amazon Web Services resource that sends logs to an Amazon Web Services destination. The destination can be CloudWatch Logs, Amazon S3, or Firehose.

• Destination

  Represents a cross-account destination that receives subscription log events.

• ExportTask

  Represents an export task.

• ExportTaskExecutionInfo

  Represents the status of an export task.

• ExportTaskStatus

  Represents the status of an export task.

• FilteredLogEvent

  Represents a matched event.

• InputLogEvent

  Represents a log event, which is a record of activity that was recorded by the application or resource being monitored.

• LogEvent

  This structure contains the information for one sample log event that is associated with an anomaly found by a log anomaly detector.

• LogGroup

  Represents a log group.

• LogGroupField

  The fields contained in log events found by a GetLogGroupFields operation, along with the percentage of queried log events in which each field appears.

• LogStream

  Represents a log stream, which is a sequence of log events from a single emitter of logs.

• MetricFilter

  Metric filters express how CloudWatch Logs would extract metric observations from ingested log events and transform them into metric data in a CloudWatch metric.

• MetricFilterMatchRecord

  Represents a matched event.

• MetricTransformation

  Indicates how to transform ingested log events to metric data in a CloudWatch metric.

• OutputLogEvent

  Represents a log event.

• PatternToken

  A tructures that contains information about one pattern token related to an anomaly.

• Policy

  A structure that contains information about one delivery destination policy.

• QueryCompileError

  Reserved.

• QueryCompileErrorLocation

  Reserved.

• QueryDefinition

  This structure contains details about a saved CloudWatch Logs Insights query definition.

• QueryInfo

  Information about one CloudWatch Logs Insights query that matches the request in a DescribeQueries operation.

• QueryStatistics

  Contains the number of log events scanned by the query, the number of log events that matched the query criteria, and the total number of bytes in the log events that were scanned.

• RejectedLogEventsInfo

  Represents the rejected events.

• ResourcePolicy

  A policy enabling one or more entities to put logs to a log group in this account.

• ResultField

  Contains one field from one log event returned by a CloudWatch Logs Insights query, along with the value of that field.

• SearchedLogStream

  Represents the search status of a log stream.

• SubscriptionFilter

  Represents a subscription filter.

• SuppressionPeriod

  If you are suppressing an anomaly temporariliy, this structure defines how long the suppression period is to be.

Enums

• AnomalyDetectorStatus
  When writing a match expression against AnomalyDetectorStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DataProtectionStatus
  When writing a match expression against DataProtectionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DeliveryDestinationType
  When writing a match expression against DeliveryDestinationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Distribution
  When writing a match expression against Distribution, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EvaluationFrequency
  When writing a match expression against EvaluationFrequency, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ExportTaskStatusCode
  When writing a match expression against ExportTaskStatusCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• InheritedProperty
  When writing a match expression against InheritedProperty, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LogGroupClass
  When writing a match expression against LogGroupClass, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OrderBy
  When writing a match expression against OrderBy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OutputFormat
  When writing a match expression against OutputFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• PolicyType
  When writing a match expression against PolicyType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• QueryStatus
  When writing a match expression against QueryStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Scope
  When writing a match expression against Scope, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StandardUnit
  When writing a match expression against StandardUnit, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• State
  When writing a match expression against State, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SuppressionState
  When writing a match expression against SuppressionState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SuppressionType
  When writing a match expression against SuppressionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SuppressionUnit
  When writing a match expression against SuppressionUnit, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.