Closed stefanjay closed 11 months ago
Hi @stefanjay Thank you for PR. Unfortunately, I'm not going to merge it. All dashboards in this repo follows the same concept, where they have dashboard variables to filter down metrics.
you can filter in the graph by clicking the volume or fix the variable query That's right, but you can end up with graph where you will have hundreds volume ids (e.g. typical enterprise environment) and you won't have a chance to click on the right one easily. This approach doesn't scale.
I believe you have some issue when you see Templating [volumeid]
- e.g. no instanceid
is selected, .... Make sure that all dashboard variables have selected right value. They depends on each other. So if you don't have instance id, then you can have correct volumeid as well.
Issue:
Added wildcard to
$volumeid
variable due to error when using cloudwatch datasource and AWS EC2 dashboard from the Grafana Dashboard Marketplace usingid 617 rev 4
.issue with variable
$volumeid
:The below query of the variable throws above error:
Environment context:
AWS EKS using grafana deployment with helm chart
kube-prom-stack
. The IAM role is defined and automated with terraform which creates a serviceaccount. The cloudwatch datasource and the dashboards are defined in the helm chart.Grafana v10.1.2
Cloudwatch roles:
Proposal:
$instanceid
+$volumeid