-
Notifications
You must be signed in to change notification settings - Fork 12k
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
variable in templating not working correctly, mabye filter not working (CloudWatch) #9940
Comments
when you change the stack parameter can you have chrome dev tools open and inspect the network traffic? There should be a call to /api/tsdb/query , can you show the request body for that call (the first one if there are multiple) |
the first one: the second one: @torkelo the instance id is always the same, doesnt matter what stack i choose |
what is the response from the first query? (the metricFindQuery) it should return an updated list of InstanceIds. Are you using the $server variable in the graph metric query? |
and when you check the server variable dropdown does it not contain those new instance ids? |
@torkelo its contain all instance ids but it have to filter the instance ids of the stack. example: choose the dev-sensu stack the filter have to scrape and show only the instance-id (i-sensu-1 , i-sensu-2) But right now its always showing all instance id`s like here in the snippet DEV-LOGSTASH-KENESIS-INPUT have only 2 id (i-04e9318d743adc4da, i-06287b499d61d5718) thats incorrect for me. |
But the metric find query returned a lot more than the 2, so either bug in cloudwatch api or the filters are not sent to aws correctly, thoughts @mtanda? |
I'll take a look. @phoppe93 I want to know the Grafana version you use. |
@mtanda |
@mtanda yes its the same it works now !! thanks ! |
Hi Grafana Team,
i tried to use the templating function to define variable. The variable are needed in the next variable. When i select a stack the server list is not updating.
Query Option "On Dashboard Load" are for both variable active.
Is there a solution or a workarround for this issue ?
The text was updated successfully, but these errors were encountered: