Tag Filtering about grafana-aws-cloudwatch-dashboards HOT 12 CLOSED

Hi,

We have imported latest change done by you but still not working.

from grafana-aws-cloudwatch-dashboards.

Thank you for idea and example. Tag filtering will be useful definitely. Let me investigate and test it.

from grafana-aws-cloudwatch-dashboards.

There will be visualization problem with ec2_instance_attribute($region, Tags, {}) if EC2 instance has more than 1 tag, example:

I would like to have 1st variable (query) which will return all tags keys and then 2nd variable (query), which will return tags values based on selected tag key (1st variable). Is it possible?

Probably we need to wait for grafana/grafana#8307

from grafana-aws-cloudwatch-dashboards.

Cool, for my use case only one Tag exists but yes I am sure others would need to filter on multple.

from grafana-aws-cloudwatch-dashboards.

@prsf1233 Check out my comment on that PR: grafana/grafana#8307 (comment)

This is how I handle the 'friendly name' issue internally.

from grafana-aws-cloudwatch-dashboards.

https://github.com/monitoringartist/grafana-aws-cloudwatch-dashboards/blob/ec2-tag-filtering/aws-ec2/aws-ec2-tag-filtering.json - EC2 dashboard with tag name filtering for Grafana 4.5.beta1+. Feel free to improve this dashboard.

from grafana-aws-cloudwatch-dashboards.

hi @jangaraj, i wanted to submit a branch and pr for this issue, but i obviously get a 403. how can i do this?

from grafana-aws-cloudwatch-dashboards.

Hi @pax-awitt, that's correct. You can push the code only to the repos, where you have write permission. Please fork this repo first and then create the pull request based on your forked and modified repo. Github help can be the useful doc for you.

from grafana-aws-cloudwatch-dashboards.

What about something like that: ec2_instance_attribute($region, Tags.Name, {}). I have checked it on 4.6.0 version.

from grafana-aws-cloudwatch-dashboards.

@tomislater That's filtering is by one tag key (Name). It's OK for simple tagging. But it can be more complicated. For example, if you have blue/green deployment. Then the Name tag value is not unique and you need to filter by additional key (Colour) as well. The best general solution for the dashboard is to have ad-hoc filters similar to Elasticsearch ad-hoc filters:

Feel free to open feature/pull request for CloudWatch plugin. Some function, which will return all available tag keys and tag values in the selected AWS "space" (ec2, ebs, emr, ...) must be implemented.

from grafana-aws-cloudwatch-dashboards.

Grafana 5 EC2 dashboard with name tag filtering b925924:

If EC2 instances don't have a Name tags, then Tag Name: All and use classic Instance ID variable to select instance.

from grafana-aws-cloudwatch-dashboards.

It looks like a IAM problem in your case. Do you have:

"ec2:DescribeTags", "ec2:DescribeInstances"

from grafana-aws-cloudwatch-dashboards.