Module aws_sdk_devopsguru::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules§
- Builders
- Error types that Amazon DevOps Guru can respond with.
Structs§
Returns the number of open reactive insights, the number of open proactive insights, and the number of metrics analyzed in your Amazon Web Services account. Use these numbers to gauge the health of operations in your Amazon Web Services account.
Information about the number of open reactive and proactive insights that can be used to gauge the health of your system.
Information about your account's integration with Amazon CodeGuru Profiler. This returns whether DevOps Guru is configured to consume recommendations generated from Amazon CodeGuru Profiler.
An Amazon CloudWatch log group that contains log anomalies and is used to generate an insight.
A time range that specifies when DevOps Guru opens and then closes an anomaly. This is different from
AnomalyTimeRange
, which specifies the time range when DevOps Guru actually observes the anomalous behavior.The Amazon Web Services resources in which DevOps Guru detected unusual behavior that resulted in the generation of an anomaly. When DevOps Guru detects multiple related anomalies, it creates and insight with details about the anomalous behavior and suggestions about how to correct the problem.
Details about the source of the anomalous operational data that triggered the anomaly.
Metadata about the detection source that generates proactive anomalies. The anomaly is detected using analysis of the metric data over a period of time
A time range that specifies when the observed unusual behavior in an anomaly started and ended. This is different from
AnomalyReportedTimeRange
, which specifies the time range when DevOps Guru opens and then closes an anomaly.Information about Amazon Web Services CloudFormation stacks. You can use up to 500 stacks to specify which Amazon Web Services resources in your account to analyze. For more information, see Stacks in the Amazon Web Services CloudFormation User Guide.
Information about Amazon Web Services CloudFormation stacks. You can use up to 500 stacks to specify which Amazon Web Services resources in your account to analyze. For more information, see Stacks in the Amazon Web Services CloudFormation User Guide.
Information about an Amazon Web Services CloudFormation stack used to create a monthly cost estimate for DevOps Guru to analyze Amazon Web Services resources. The maximum number of stacks you can specify for a cost estimate is one. The estimate created is for the cost to analyze the Amazon Web Services resources defined by the stack. For more information, see Stacks in the Amazon Web Services CloudFormation User Guide.
Information about the health of Amazon Web Services resources in your account that are specified by an Amazon Web Services CloudFormation stack.
Contains information about the analyzed metrics that displayed anomalous behavior.
Information about an Amazon CloudWatch metric.
The dimension of an Amazon CloudWatch metric that is used when DevOps Guru analyzes the resources in your account for operational problems and anomalous behavior. A dimension is a name/value pair that is part of the identity of a metric. A metric can have up to 10 dimensions. For more information, see Dimensions in the Amazon CloudWatch User Guide.
Information about a filter used to specify which Amazon Web Services resources are analyzed to create a monthly DevOps Guru cost estimate. For more information, see Estimate your Amazon DevOps Guru costs and Amazon DevOps Guru pricing.
The time range of a cost estimation.
A range of time that specifies when anomalous behavior in an anomaly or insight ended.
An Amazon Web Services resource event. Amazon Web Services resource events and metrics are analyzed by DevOps Guru to find anomalous behavior and provide recommendations to improve your operational solutions.
The Amazon Web Services resource that emitted an event. Amazon Web Services resource events and metrics are analyzed by DevOps Guru to find anomalous behavior and provide recommendations to improve your operational solutions.
Information about the integration of DevOps Guru as consumer with another AWS service, such as AWS CodeGuru Profiler via EventBridge.
The time range during which an Amazon Web Services event occurred. Amazon Web Services resource events and metrics are analyzed by DevOps Guru to find anomalous behavior and provide recommendations to improve your operational solutions.
Information about insight feedback received from a customer.
Information about the number of open reactive and proactive insights that can be used to gauge the health of your system.
A time ranged that specifies when the observed behavior in an insight started and ended.
Information about the KMS encryption used with DevOps Guru.
Information about whether DevOps Guru is configured to encrypt server-side data using KMS.
Specifies one or more service names that are used to list anomalies.
Filters you can use to specify which events are returned when
ListEvents
is called.Used to filter for insights that have any status.
Used to filter for insights that have the status
CLOSED
.Used to filter for insights that have the status
ONGOING
.A filter used by
ListInsights
to specify which insights to return.Filters to determine which monitored resources you want to retrieve. You can filter by resource type or resource permission status.
Information about an anomalous log event found within a log group.
A cluster of similar anomalous log events found within a log group.
Information about the integration of DevOps Guru with CloudWatch log groups for log anomaly detection.
Information about the integration of DevOps Guru with CloudWatch log groups for log anomaly detection. You can use this to update the configuration.
Information about the resource that is being monitored, including the name of the resource, the type of resource, and whether or not permission is given to DevOps Guru to access that resource.
Information about a notification channel. A notification channel is used to notify you when DevOps Guru creates an insight. The one supported notification channel is Amazon Simple Notification Service (Amazon SNS).
Information about notification channels you have configured with DevOps Guru. The one supported notification channel is Amazon Simple Notification Service (Amazon SNS).
The filter configurations for the Amazon SNS notification topic you use with DevOps Guru. You can choose to specify which events or message types to receive notifications for. You can also choose to specify which severity levels to receive notifications for.
Information about whether DevOps Guru is configured to create an OpsItem in Amazon Web Services Systems Manager OpsCenter for each created insight.
Information about whether DevOps Guru is configured to create an OpsItem in Amazon Web Services Systems Manager OpsCenter for each created insight. You can use this to update the configuration.
A logical grouping of Performance Insights metrics for a related subject area. For example, the
db.sql
dimension group consists of the following dimensions:db.sql.id
,db.sql.db_id
,db.sql.statement
, anddb.sql.tokenized_id
.A single query to be processed. Use these parameters to query the Performance Insights
GetResourceMetrics
API to retrieve the metrics for an anomaly. For more information, seeGetResourceMetrics
in the Amazon RDS Performance Insights API Reference.Details about Performance Insights metrics.
Reference scalar values and other metrics that DevOps Guru displays on a graph in its console along with the actual metrics it analyzed. Compare these reference values to your actual metrics to help you understand anomalous behavior that DevOps Guru detected.
Reference data used to evaluate Performance Insights to determine if its performance is anomalous or not.
Information about a reference metric used to evaluate Performance Insights.
A reference value to compare Performance Insights metrics against to determine if the metrics demonstrate anomalous behavior.
A statistic in a Performance Insights collection.
The time range during which anomalous behavior in a proactive anomaly or an insight is expected to occur.
Information about an anomaly. This object is returned by
ListAnomalies
.Details about a proactive anomaly. This object is returned by
DescribeAnomaly.
Details about a proactive insight. This object is returned by
ListInsights
.Details about a proactive insight. This object is returned by
DescribeInsight.
Details about a proactive insight. This object is returned by
DescribeInsight
.Details about a reactive anomaly. This object is returned by
ListAnomalies
.Details about a reactive anomaly. This object is returned by
DescribeAnomaly.
Information about a reactive insight. This object is returned by
ListInsights
.Information about a reactive insight. This object is returned by
DescribeInsight.
Information about a reactive insight. This object is returned by
DescribeInsight
.Recommendation information to help you remediate detected anomalous behavior that generated an insight.
Information about an anomaly that is related to a recommendation.
Information about a resource in which DevOps Guru detected anomalous behavior.
Contains an array of
RecommendationRelatedCloudWatchMetricsSourceDetail
objects that contain the name and namespace of an Amazon CloudWatch metric.Information about an Amazon CloudWatch metric that is analyzed by DevOps Guru. It is one of many analyzed metrics that are used to generate insights.
Information about an event that is related to a recommendation.
Information about an Amazon Web Services resource that emitted and event that is related to a recommendation in an insight.
A collection of Amazon Web Services resources supported by DevOps Guru. The two types of Amazon Web Services resource collections supported are Amazon Web Services CloudFormation stacks and Amazon Web Services resources that contain the same Amazon Web Services tag. DevOps Guru can be configured to analyze the Amazon Web Services resources that are defined in the stacks or that are tagged using the same tag key. You can specify up to 500 Amazon Web Services CloudFormation stacks.
Information about a filter used to specify which Amazon Web Services resources are analyzed for anomalous behavior by DevOps Guru.
Specifies values used to filter responses when searching for insights. You can use a
ResourceCollection
,ServiceCollection
, array of severities, and an array of status values. Each filter type contains one or more values to search for. If you specify multiple filter types, the filter types are joined with anAND
, and the request returns only results that match all of the specified filters.Filters you can use to specify which events are returned when
ListEvents
is called.A collection of the names of Amazon Web Services services.
Represents the health of an Amazon Web Services service.
Contains the number of open proactive and reactive insights in an analyzed Amazon Web Services service.
Information about the integration of DevOps Guru with another Amazon Web Services service, such as Amazon Web Services Systems Manager.
An object that contains information about the estimated monthly cost to analyze an Amazon Web Services resource. For more information, see Estimate your Amazon DevOps Guru costs and Amazon DevOps Guru pricing.
Contains the Amazon Resource Name (ARN) of an Amazon Simple Notification Service topic.
A time range used to specify when the behavior of an insight or anomaly started.
A collection of Amazon Web Services tags.
A collection of Amazon Web Services tags used to filter insights. This is used to return insights generated from only resources that contain the tags in the tag collection.
Information about a collection of Amazon Web Services resources that are identified by an Amazon Web Services tag. This collection of resources is used to create a monthly cost estimate for DevOps Guru to analyze Amazon Web Services resources. The maximum number of tags you can specify for a cost estimate is one. The estimate created is for the cost to analyze the Amazon Web Services resources defined by the tag. For more information, see Stacks in the Amazon Web Services CloudFormation User Guide.
Information about the health of Amazon Web Services resources in your account that are specified by an Amazon Web Services tag key.
A pair that contains metric values at the respective timestamp.
Contains the names of Amazon Web Services CloudFormation stacks used to update a collection of stacks. You can specify up to 500 Amazon Web Services CloudFormation stacks.
Contains information used to update a collection of Amazon Web Services resources.
Information about updating the integration status of an Amazon Web Services service, such as Amazon Web Services Systems Manager, with DevOps Guru.
A new collection of Amazon Web Services resources that are defined by an Amazon Web Services tag or tag key/value pair.
The field associated with the validation exception.
Enums§
- When writing a match expression against
AnomalySeverity
, 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. - When writing a match expression against
AnomalyStatus
, 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. - When writing a match expression against
AnomalyType
, 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. - When writing a match expression against
CloudWatchMetricDataStatusCode
, 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. - When writing a match expression against
CloudWatchMetricsStat
, 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. - When writing a match expression against
CostEstimationServiceResourceState
, 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. - When writing a match expression against
CostEstimationStatus
, 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. - When writing a match expression against
EventClass
, 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. - When writing a match expression against
EventDataSource
, 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. - When writing a match expression against
EventSourceOptInStatus
, 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. - When writing a match expression against
InsightFeedbackOption
, 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. - When writing a match expression against
InsightSeverity
, 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. - When writing a match expression against
InsightStatus
, 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. - When writing a match expression against
InsightType
, 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. - When writing a match expression against
Locale
, 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. - When writing a match expression against
LogAnomalyType
, 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. - When writing a match expression against
NotificationMessageType
, 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. - When writing a match expression against
OptInStatus
, 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. - When writing a match expression against
OrganizationResourceCollectionType
, 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. - When writing a match expression against
ResourceCollectionType
, 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. - When writing a match expression against
ResourcePermission
, 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. - When writing a match expression against
ResourceTypeFilter
, 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. - When writing a match expression against
ServerSideEncryptionType
, 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. - When writing a match expression against
ServiceName
, 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. - When writing a match expression against
UpdateResourceCollectionAction
, 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. - When writing a match expression against
ValidationExceptionReason
, 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.