Skip to content

Why is monitorElasticCache part of default monitoring when using monitorScope? #446

Answered by echeung-amzn
larskinder asked this question in Q&A
Discussion options

You must be logged in to vote

Unfortunately the implementation of ElastiCacheClusterMonitoring/ElastiCacheClusterMetricFactory relied on a plain clusterId to identity the clusters rather than any concrete construct nodes. That may be subject to change if L2 constructs for ElastiCache are ever made available.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by larskinder
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants