Skip to content

Commit

Permalink
Update API model
Browse files Browse the repository at this point in the history
  • Loading branch information
AWS SDK for Go v2 automation user committed Feb 23, 2024
1 parent 6397a64 commit ca190b0
Show file tree
Hide file tree
Showing 4 changed files with 71 additions and 61 deletions.
10 changes: 5 additions & 5 deletions codegen/sdk-codegen/aws-models/appsync.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2250,7 +2250,7 @@
"healthMetricsConfig": {
"target": "com.amazonaws.appsync#CacheHealthMetricsConfig",
"traits": {
"smithy.api#documentation": "<p>Controls how cache health metrics will be emitted to CloudWatch. Cache health metrics include:</p>\n <ul>\n <li>\n <p>NetworkBandwidthOutAllowanceExceeded: The number of times a specified GraphQL operation was\n called.</p>\n </li>\n <li>\n <p>EngineCPUUtilization: The number of GraphQL errors that occurred during a specified GraphQL\n operation.</p>\n </li>\n </ul>\n <p>Metrics will be recorded by API ID. You can set the value to <code>ENABLED</code> or\n <code>DISABLED</code>.</p>"
"smithy.api#documentation": "<p>Controls how cache health metrics will be emitted to CloudWatch. Cache health metrics include:</p>\n <ul>\n <li>\n <p>NetworkBandwidthOutAllowanceExceeded: The network packets dropped because the throughput exceeded\n the aggregated bandwidth limit. This is useful for diagnosing bottlenecks in a cache\n configuration.</p>\n </li>\n <li>\n <p>EngineCPUUtilization: The CPU utilization (percentage) allocated to the Redis process. This is\n useful for diagnosing bottlenecks in a cache configuration.</p>\n </li>\n </ul>\n <p>Metrics will be recorded by API ID. You can set the value to <code>ENABLED</code> or\n <code>DISABLED</code>.</p>"
}
}
},
Expand Down Expand Up @@ -4331,14 +4331,14 @@
"resolverLevelMetricsBehavior": {
"target": "com.amazonaws.appsync#ResolverLevelMetricsBehavior",
"traits": {
"smithy.api#documentation": "<p>Controls how resolver metrics will be emitted to CloudWatch. Resolver metrics include:</p>\n <ul>\n <li>\n <p>GraphQL errors: The number of GraphQL errors that occurred.</p>\n </li>\n <li>\n <p>Requests: The number of invocations that occurred during a request. </p>\n </li>\n <li>\n <p>Latency: The time to complete a resolver invocation.</p>\n </li>\n <li>\n <p>Cache hits: The number of cache hits during a request.</p>\n </li>\n <li>\n <p>Cache misses: The number of cache misses during a request.</p>\n </li>\n </ul>\n <p>These metrics can be emitted to CloudWatch per resolver or for all resolvers in the request. Metrics will be\n recorded by API ID and resolver name. <code>resolverLevelMetricsBehavior</code> accepts one of these values at\n a time:</p>\n <ul>\n <li>\n <p>\n <code>FULL_REQUEST_RESOLVER_METRICS</code>: Records and emits metric data for all resolvers in the\n request.</p>\n </li>\n <li>\n <p>\n <code>PER_RESOLVER_METRICS</code>: Records and emits metric data for resolvers that have the\n <code>metricConfig</code> value set to <code>ENABLED</code>.</p>\n </li>\n </ul>",
"smithy.api#documentation": "<p>Controls how resolver metrics will be emitted to CloudWatch. Resolver metrics include:</p>\n <ul>\n <li>\n <p>GraphQL errors: The number of GraphQL errors that occurred.</p>\n </li>\n <li>\n <p>Requests: The number of invocations that occurred during a request. </p>\n </li>\n <li>\n <p>Latency: The time to complete a resolver invocation.</p>\n </li>\n <li>\n <p>Cache hits: The number of cache hits during a request.</p>\n </li>\n <li>\n <p>Cache misses: The number of cache misses during a request.</p>\n </li>\n </ul>\n <p>These metrics can be emitted to CloudWatch per resolver or for all resolvers in the request. Metrics will be\n recorded by API ID and resolver name. <code>resolverLevelMetricsBehavior</code> accepts one of these values at\n a time:</p>\n <ul>\n <li>\n <p>\n <code>FULL_REQUEST_RESOLVER_METRICS</code>: Records and emits metric data for all resolvers in the\n request.</p>\n </li>\n <li>\n <p>\n <code>PER_RESOLVER_METRICS</code>: Records and emits metric data for resolvers that have the\n <code>metricsConfig</code> value set to <code>ENABLED</code>.</p>\n </li>\n </ul>",
"smithy.api#required": {}
}
},
"dataSourceLevelMetricsBehavior": {
"target": "com.amazonaws.appsync#DataSourceLevelMetricsBehavior",
"traits": {
"smithy.api#documentation": "<p>Controls how data source metrics will be emitted to CloudWatch. Data source metrics include:</p>\n <ul>\n <li>\n <p>Requests: The number of invocations that occured during a request.</p>\n </li>\n <li>\n <p>Latency: The time to complete a data source invocation.</p>\n </li>\n <li>\n <p>Errors: The number of errors that occurred during a data source invocation.</p>\n </li>\n </ul>\n <p>These metrics can be emitted to CloudWatch per data source or for all data sources in the request. Metrics\n will be recorded by API ID and data source name. <code>dataSourceLevelMetricsBehavior</code> accepts one of\n these values at a time:</p>\n <ul>\n <li>\n <p>\n <code>FULL_REQUEST_DATA_SOURCE_METRICS</code>: Records and emits metric data for all data sources\n in the request.</p>\n </li>\n <li>\n <p>\n <code>PER_DATA_SOURCE_METRICS</code>: Records and emits metric data for data sources that have the\n <code>metricConfig</code> value set to <code>ENABLED</code>.</p>\n </li>\n </ul>",
"smithy.api#documentation": "<p>Controls how data source metrics will be emitted to CloudWatch. Data source metrics include:</p>\n <ul>\n <li>\n <p>Requests: The number of invocations that occured during a request.</p>\n </li>\n <li>\n <p>Latency: The time to complete a data source invocation.</p>\n </li>\n <li>\n <p>Errors: The number of errors that occurred during a data source invocation.</p>\n </li>\n </ul>\n <p>These metrics can be emitted to CloudWatch per data source or for all data sources in the request. Metrics\n will be recorded by API ID and data source name. <code>dataSourceLevelMetricsBehavior</code> accepts one of\n these values at a time:</p>\n <ul>\n <li>\n <p>\n <code>FULL_REQUEST_DATA_SOURCE_METRICS</code>: Records and emits metric data for all data sources\n in the request.</p>\n </li>\n <li>\n <p>\n <code>PER_DATA_SOURCE_METRICS</code>: Records and emits metric data for data sources that have the\n <code>metricsConfig</code> value set to <code>ENABLED</code>.</p>\n </li>\n </ul>",
"smithy.api#required": {}
}
},
Expand All @@ -4351,7 +4351,7 @@
}
},
"traits": {
"smithy.api#documentation": "<p>Enables and controls the enhanced metrics feature. Enhanced metrics emit granular data on API usage and\n performance such as AppSync request and error counts, latency, and cache hits/misses. All enhanced metric data\n is sent to your CloudWatch account, and you can configure the types of data that will be sent. </p>\n <p>Enhanced metrics can be configured at the resolver, data source, and operation levels.\n <code>EnhancedMetricsConfig</code> contains three required parameters, each controlling one of these\n categories:</p>\n <ol>\n <li>\n <p>\n <code>resolverLevelMetricsBehavior</code>: Controls how resolver metrics will be emitted to\n CloudWatch. Resolver metrics include:</p>\n <ul>\n <li>\n <p>GraphQL errors: The number of GraphQL errors that occurred.</p>\n </li>\n <li>\n <p>Requests: The number of invocations that occurred during a request. </p>\n </li>\n <li>\n <p>Latency: The time to complete a resolver invocation.</p>\n </li>\n <li>\n <p>Cache hits: The number of cache hits during a request.</p>\n </li>\n <li>\n <p>Cache misses: The number of cache misses during a request.</p>\n </li>\n </ul>\n <p>These metrics can be emitted to CloudWatch per resolver or for all resolvers in the request. Metrics\n will be recorded by API ID and resolver name. <code>resolverLevelMetricsBehavior</code> accepts one of\n these values at a time:</p>\n <ul>\n <li>\n <p>\n <code>FULL_REQUEST_RESOLVER_METRICS</code>: Records and emits metric data for all resolvers\n in the request.</p>\n </li>\n <li>\n <p>\n <code>PER_RESOLVER_METRICS</code>: Records and emits metric data for resolvers that have the\n <code>metricConfig</code> value set to <code>ENABLED</code>.</p>\n </li>\n </ul>\n </li>\n <li>\n <p>\n <code>dataSourceLevelMetricsBehavior</code>: Controls how data source metrics will be emitted to\n CloudWatch. Data source metrics include:</p>\n <ul>\n <li>\n <p>Requests: The number of invocations that occured during a request.</p>\n </li>\n <li>\n <p>Latency: The time to complete a data source invocation.</p>\n </li>\n <li>\n <p>Errors: The number of errors that occurred during a data source invocation.</p>\n </li>\n </ul>\n <p>These metrics can be emitted to CloudWatch per data source or for all data sources in the request.\n Metrics will be recorded by API ID and data source name. <code>dataSourceLevelMetricsBehavior</code>\n accepts one of these values at a time:</p>\n <ul>\n <li>\n <p>\n <code>FULL_REQUEST_DATA_SOURCE_METRICS</code>: Records and emits metric data for all data\n sources in the request.</p>\n </li>\n <li>\n <p>\n <code>PER_DATA_SOURCE_METRICS</code>: Records and emits metric data for data sources that\n have the <code>metricConfig</code> value set to <code>ENABLED</code>.</p>\n </li>\n </ul>\n </li>\n <li>\n <p>\n <code>operationLevelMetricsConfig</code>: Controls how operation metrics will be emitted to\n CloudWatch. Operation metrics include:</p>\n <ul>\n <li>\n <p>Requests: The number of times a specified GraphQL operation was called.</p>\n </li>\n <li>\n <p>GraphQL errors: The number of GraphQL errors that occurred during a specified GraphQL\n operation.</p>\n </li>\n </ul>\n <p>Metrics will be recorded by API ID and operation name. You can set the value to <code>ENABLED</code>\n or <code>DISABLED</code>.</p>\n </li>\n </ol>"
"smithy.api#documentation": "<p>Enables and controls the enhanced metrics feature. Enhanced metrics emit granular data on API usage and\n performance such as AppSync request and error counts, latency, and cache hits/misses. All enhanced metric data\n is sent to your CloudWatch account, and you can configure the types of data that will be sent. </p>\n <p>Enhanced metrics can be configured at the resolver, data source, and operation levels.\n <code>EnhancedMetricsConfig</code> contains three required parameters, each controlling one of these\n categories:</p>\n <ol>\n <li>\n <p>\n <code>resolverLevelMetricsBehavior</code>: Controls how resolver metrics will be emitted to\n CloudWatch. Resolver metrics include:</p>\n <ul>\n <li>\n <p>GraphQL errors: The number of GraphQL errors that occurred.</p>\n </li>\n <li>\n <p>Requests: The number of invocations that occurred during a request. </p>\n </li>\n <li>\n <p>Latency: The time to complete a resolver invocation.</p>\n </li>\n <li>\n <p>Cache hits: The number of cache hits during a request.</p>\n </li>\n <li>\n <p>Cache misses: The number of cache misses during a request.</p>\n </li>\n </ul>\n <p>These metrics can be emitted to CloudWatch per resolver or for all resolvers in the request. Metrics\n will be recorded by API ID and resolver name. <code>resolverLevelMetricsBehavior</code> accepts one of\n these values at a time:</p>\n <ul>\n <li>\n <p>\n <code>FULL_REQUEST_RESOLVER_METRICS</code>: Records and emits metric data for all resolvers\n in the request.</p>\n </li>\n <li>\n <p>\n <code>PER_RESOLVER_METRICS</code>: Records and emits metric data for resolvers that have the\n <code>metricsConfig</code> value set to <code>ENABLED</code>.</p>\n </li>\n </ul>\n </li>\n <li>\n <p>\n <code>dataSourceLevelMetricsBehavior</code>: Controls how data source metrics will be emitted to\n CloudWatch. Data source metrics include:</p>\n <ul>\n <li>\n <p>Requests: The number of invocations that occured during a request.</p>\n </li>\n <li>\n <p>Latency: The time to complete a data source invocation.</p>\n </li>\n <li>\n <p>Errors: The number of errors that occurred during a data source invocation.</p>\n </li>\n </ul>\n <p>These metrics can be emitted to CloudWatch per data source or for all data sources in the request.\n Metrics will be recorded by API ID and data source name. <code>dataSourceLevelMetricsBehavior</code>\n accepts one of these values at a time:</p>\n <ul>\n <li>\n <p>\n <code>FULL_REQUEST_DATA_SOURCE_METRICS</code>: Records and emits metric data for all data\n sources in the request.</p>\n </li>\n <li>\n <p>\n <code>PER_DATA_SOURCE_METRICS</code>: Records and emits metric data for data sources that\n have the <code>metricsConfig</code> value set to <code>ENABLED</code>.</p>\n </li>\n </ul>\n </li>\n <li>\n <p>\n <code>operationLevelMetricsConfig</code>: Controls how operation metrics will be emitted to\n CloudWatch. Operation metrics include:</p>\n <ul>\n <li>\n <p>Requests: The number of times a specified GraphQL operation was called.</p>\n </li>\n <li>\n <p>GraphQL errors: The number of GraphQL errors that occurred during a specified GraphQL\n operation.</p>\n </li>\n </ul>\n <p>Metrics will be recorded by API ID and operation name. You can set the value to <code>ENABLED</code>\n or <code>DISABLED</code>.</p>\n </li>\n </ol>"
}
},
"com.amazonaws.appsync#EnvironmentVariableKey": {
Expand Down Expand Up @@ -8422,7 +8422,7 @@
"healthMetricsConfig": {
"target": "com.amazonaws.appsync#CacheHealthMetricsConfig",
"traits": {
"smithy.api#documentation": "<p>Controls how cache health metrics will be emitted to CloudWatch. Cache health metrics include:</p>\n <ul>\n <li>\n <p>NetworkBandwidthOutAllowanceExceeded: The number of times a specified GraphQL operation was\n called.</p>\n </li>\n <li>\n <p>EngineCPUUtilization: The number of GraphQL errors that occurred during a specified GraphQL\n operation.</p>\n </li>\n </ul>\n <p>Metrics will be recorded by API ID. You can set the value to <code>ENABLED</code> or\n <code>DISABLED</code>.</p>"
"smithy.api#documentation": "<p>Controls how cache health metrics will be emitted to CloudWatch. Cache health metrics include:</p>\n <ul>\n <li>\n <p>NetworkBandwidthOutAllowanceExceeded: The network packets dropped because the throughput exceeded\n the aggregated bandwidth limit. This is useful for diagnosing bottlenecks in a cache\n configuration.</p>\n </li>\n <li>\n <p>EngineCPUUtilization: The CPU utilization (percentage) allocated to the Redis process. This is\n useful for diagnosing bottlenecks in a cache configuration.</p>\n </li>\n </ul>\n <p>Metrics will be recorded by API ID. You can set the value to <code>ENABLED</code> or\n <code>DISABLED</code>.</p>"
}
}
},
Expand Down
Loading

0 comments on commit ca190b0

Please sign in to comment.