opensource/grafana
1
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-07-30 08:22:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

Change metadata of doc topics (#27943)

Browse Source 
* Changes. to metadata in Manage users

* changes to install section

* Added titile

* More changes.

* Updated administration folder metadata, moved 2 files from installation folder.

* Added links to Administration landing page, other metadata changes worked out.

* Updated alerting section metadata.

* Updated metadata of Auth section. Broke index and created separate Grafana Authentication section.

* Added correct weight.

* Updated metadata for the Best practices section.

* Updated metadata in templates, broke Overview topic.

* Updated subment Variable types metadata

* Fixed yaml file and H1 description of Variables syntax topic.

* Couple more metadata changes.

* Added aliases files, as suggested by Diana.
This commit is contained in:
achatterjee-grafana
2020-10-01 17:37:26 -04:00
committed by GitHub
parent 715f0133ee
commit add777ad40
80 changed files with 365 additions and 303 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/sources/variables/variable-selection-options.md
View File

@ -2,7 +2,9 @@
title = "Enter variable Selection Options"
type = "docs"
[menu.docs]
weight = 800
identifier = "variables-selection-options"
parent = "variables"
weight = 400
+++
# Enter variable selection options
@ -25,4 +27,4 @@ Enter regex, globs, or lucene syntax in the **Custom all value** field to define
By default the `All` value includes all options in combined expression. This can become very long and can have performance problems. Sometimes it can be better to specify a custom all value, like a wildcard regex.
In order to have custom regex, globs, or lucene syntax in the **Custom all value** option, it is never escaped so you will have to think about what is a valid value for your data source.
In order to have custom regex, globs, or lucene syntax in the **Custom all value** option, it is never escaped so you will have to think about what is a valid value for your data source.