From 564a34a9c8fdfbb66c7a891a8cdb1ab7207abf59 Mon Sep 17 00:00:00 2001 From: Mohit Nain Date: Thu, 25 Jun 2020 16:24:21 +0530 Subject: [PATCH] Update docs/sources/variables/templates-and-variables.md (#25829) * Update docs/sources/variables/templates-and-variables.md Co-authored-by: Arve Knudsen --- docs/sources/variables/templates-and-variables.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sources/variables/templates-and-variables.md b/docs/sources/variables/templates-and-variables.md index 96fb5395e87..6710b0caba8 100644 --- a/docs/sources/variables/templates-and-variables.md +++ b/docs/sources/variables/templates-and-variables.md @@ -202,7 +202,7 @@ Option | Description ### Formatting multiple values -Interpolating a variable with multiple values selected is tricky as it is not straight forward how to format the multiple values into a string that +Interpolating a variable with multiple values selected is tricky, as it is not straightforward how to format the multiple values into a string that is valid in the given context where the variable is used. Grafana tries to solve this by allowing each data source plugin to inform the templating interpolation engine what format to use for multiple values. @@ -220,7 +220,7 @@ needs to be escaped so that the value can contain lucene control words and quota #### Formatting troubles -Automatic escaping and formatting can cause problems and it can be tricky to grasp the logic is behind it. +Automatic escaping and formatting can cause problems and it can be tricky to grasp the logic behind it. Especially for InfluxDB and Prometheus where the use of regex syntax requires that the variable is used in regex operator context. If you do not want Grafana to do this automatic regex escaping and formatting your only option is to disable the *Multi-value* or *Include All option* options.