usecase

The concern is documenting getting consul queries in grafana

1. variables

1.1. create consul datasource

  • create a Consul variable as a datasource type → select Consul
  • difference is that here, you can use also KEYS (not tree leaves) as values

add_consul_as_datasource

1.2. create consul query

  • create a ConsulQuery variable as a query → select $Consul as a datasource
  • but how could I create the queries made out of variables - well, most probably
  • you have to be using those, the only variable I can think of is, however, only customer, can you create another one

http://pavol.kutaj.com/assets/img001993.png

2. queries

  • You can just query consul
  • here I would like to know now many nodes each client has in their ES cluster

2.1. navigation: no whitespace, relative paths

  • in columns, no spaces are allowed
  • navigate with relative paths

2.2. retrieve key directly

storage_size

2.3. get selected keys from a parent node

  • either select a leaf such as
customer/${customer}/aws_elasticsearch_prod1/input/volume_size
  • and then add another leaves to is in columns
./,../instance_count/,../instance_type/

select_one_add_more

2.4. columns

  • seems like that is going from the query

storage_size

  • so if you query
customer/*/aws_setup_prod1/input/client_name
  • you put the following as columns
./,../uuid
  • to have the result of the query as a columns in and of itself, use ./

getting_the_paths_correct