From 24e527ae0264e1f6bee34c749c8644f8bc313450 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Torkel=20=C3=96degaard?= Date: Tue, 7 Jul 2015 14:50:23 +0200 Subject: [PATCH] Updated Graphite docs, Closes #2271 --- docs/sources/datasources/graphite.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/sources/datasources/graphite.md b/docs/sources/datasources/graphite.md index 368feeda8c3..05a4891c581 100644 --- a/docs/sources/datasources/graphite.md +++ b/docs/sources/datasources/graphite.md @@ -57,3 +57,16 @@ this consolidation is done using `avg` function. You can how graphite consolidat > *Notice* This means that legend summary values (max, min, total) cannot be all correct at the same time. They are calculated > client side by Grafana. And depending on your consolidation function only one or two can be correct at the same time. + +## Templating +You can create a template variable in Grafana and have that variable filled with values from any Graphite metric exploration query. +You can then use this variable in your Graphite queries, either as part of a metric path or as arguments to functions. + +For example a query like `prod.servers.*` will fill the variable with all possible +values that exists in the wildcard position. + +You can also create nested variables that use other variables in their definition. For example +`apps.$app.servers.*` uses the variable `$app` in its query definition. + +![](/img/v2/templated_variable_parameter.png) +