Skip to content
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

[Bug] 4.6.0-beta3 breaks cloudwatch templating filters #9667

Closed
chrono opened this issue Oct 25, 2017 · 6 comments
Closed

[Bug] 4.6.0-beta3 breaks cloudwatch templating filters #9667

chrono opened this issue Oct 25, 2017 · 6 comments

Comments

@chrono
Copy link

chrono commented Oct 25, 2017

A templating query like ec2_instance_attribute(us-east-1, Tags.Name, { "tag:Environment": ["production"] }) should return results filtered by Environment tag.

It doesn't seem to apply any filters at all.

CloudWatch datasource, Grafana v4.6.0-beta3 (commit: 9a91a88)

@bergquist bergquist modified the milestones: 4.6.0-beta4, 4.6.1 Oct 26, 2017
@torkelo
Copy link
Member

torkelo commented Oct 26, 2017

@mtanda is this something you could take a look at?

@TryTryAgain
Copy link

Would this be related to 4.6.0 breaking my templates which are like:

$region | regions()
$LinkedAccount | dimension_values($region, AWS/Billing, EstimatedCharges, LinkedAccount)
$ServiceName | dimension_values($region, AWS/Billing, EstimatedCharges, ServiceName)

I use that to see all possible services for all accounts out of our master billing account which has all the linked accounts through it. Now I'm getting Metric request error

@vasdee
Copy link

vasdee commented Oct 28, 2017

I can confirm this has been broken for all the 4.6 beta builds and the final 4.6 build. I had assumed this was an issue on my aws credentials until I saw this issue

@csghuser
Copy link

csghuser commented Nov 6, 2017

This appears to be broken in 4.6.0 for us. Filters have no effect.

@jdkindy
Copy link

jdkindy commented Nov 10, 2017

This is an issue with 4.6.1

@torkelo torkelo closed this as completed Nov 13, 2017
@torkelo
Copy link
Member

torkelo commented Nov 13, 2017

fixed by #9718

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants