-
Notifications
You must be signed in to change notification settings - Fork 12.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CloudWatch: High resolution is not work #20436
Comments
Thanks @mtanda for reporting this! |
Thanks for reporting this @mtanda. I'm afraid I don't see how we could support HighRes now that we use GMD instead of GMS. The reason is that even though there's plenty of queries in the panel, we only make one call to GetMetricData API. That call uses the same startTime and endTime for all queries, so really there's no way to define HighRes on a per query level anymore. Or do you have any solution to this @mtanda? That is something that does not include multiple GMD calls. So the error message that you've received is expected - a workaround is to reduce the timespan. I suggest I remove the HighRes toggle from the GUI and also describe this as a breaking change in the changelog. |
@mtanda I'm also available on grafanas public slack if you'd prefer to discuss this over there. |
I send a partial fix of this issue. If the query doesn't include expression, datasource can handle high resolution. |
The hardest limitation of CloudWatch API is, NextToken is not returned when query has expression. https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_MetricDataResult.html
New GMD implementation utilize |
What happened:
High resolution query cause error.
The error message is
too many datapoint requested in query A. Please try to reduce the time range
.What you expected to happen:
Get success response.
How to reproduce it (as minimally and precisely as possible):
100800 / ((60 / 5) * 24 * 30) = 11.6
, select 12 InstanceIdAnything else we need to know?:
Original implementation is #10925 .
Environment:
The text was updated successfully, but these errors were encountered: