- Newest
- Most votes
- Most comments
You're correct that there is a limit on the number of metrics that can be processed and returned by CloudWatch Metrics Insights queries, which includes SEARCH expressions. This limit is indeed documented, though it may not be immediately obvious where to find it.
The limit you're encountering is that a single query can process no more than 10,000 metrics. If your SEARCH expression matches more than 10,000 metrics, only the first 10,000 that it finds will be processed.
Additionally, there's another relevant limit: a single query can return no more than 500 time series. This means that even if your query processes up to 10,000 metrics, the results will be limited to 500 time series.
These limits apply to CloudWatch Metrics Insights queries, which include SEARCH expressions used in dashboards and other CloudWatch features.
Regarding your specific asks:
-
The limit is documented in the CloudWatch documentation, specifically in the section about CloudWatch Metrics Insights limits.
-
Your suggestion to make this information more easily discoverable is valid. It would indeed be helpful if these limits were more prominently displayed or cross-referenced in related documentation, such as the pages you mentioned (Values.fromSearch, search expression syntax, and service quotas).
To work around these limits in your dashboard, you might consider:
- Narrowing your search criteria to reduce the number of matching metrics
- Using multiple widgets with more specific searches if you need to display more than 500 time series
- If possible, restructuring your metrics to reduce the total number while still capturing the necessary information
It's worth noting that these limits are in place to ensure performance and prevent excessive resource consumption, as processing and returning large numbers of metrics can be computationally expensive.
Sources
Metrics Insights limits - Amazon CloudWatch
CloudWatch observability solutions - Amazon CloudWatch
Using the metric query option to query CloudWatch Metrics Insights data - Amazon Managed Grafana
Relevant content
asked 3 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 5 months ago

The AI agrees with me: please improve the documentation