[Enhancement]: AppSync Enhanced Monitoring

[alexmoore0]

Description

AWS announced support for AppSync Enhanced Monitoring in February 2024 to provide data-source-level, resolver-level, and operation-level metrics such as latency, requests, and errors.

Currently, given an aws_appsync_graphql_api resource provisioned with terraform, if you enable Enhanced Monitoring via the AWS Console, re-applying the aws_appsync_graphql_api resource will disable Enhanced Monitoring.

Affected Resource(s) and/or Data Source(s)

• aws_appsync_graphql_api

Potential Terraform Configuration

resource aws_appsync_graphql_api appsync {
  enhanced_monitoring {
    resolver_metrics_behavior    = "per-resolver" | "full"
    data_source_metrics_behavior = "per-data-source" | "full"
    operation_metrics_behavior   = true | false
  }
}

References

AWS Announcement

Cloudwatch docs

Info from AWS Console

Enhanced Monitoring
By default, your API has basic monitoring enabled. You can optionally enable enhanced monitoring for an additional charge.
Enhanced monitoring provides additional granular metrics to give more detailed visibility into your AppSync usage. You can configure extra enhanced metrics for your resolvers, data sources, and GraphQL operations.
For resolver and data source metrics, you can choose to enable metrics on all resources ("Full Request Resolver Metrics" and "Full Request Data Source Metrics"). Alternatively, select "Per Resolver" to configure metrics for specific resolvers only or "Per Data Source" to add metrics for particular data sources.
See the AppSync documentation for a list of supported enhanced metrics.

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.61.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.