From fc42013dad825662351a789e1f8af1a699984d25 Mon Sep 17 00:00:00 2001 From: aSquare14 Date: Sun, 18 Apr 2021 22:18:51 +0530 Subject: [PATCH] fixup examples Signed-off-by: aSquare14 --- docs/configuration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configuration.md b/docs/configuration.md index e9b2a8a3..910f6534 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -603,19 +603,19 @@ Here are some examples of valid string matchers : 2. Similar to example 1, shown below are two equality matchers combined in a short form YAML list. ```yaml -matchers: [ "foo = bar", "dings != bums" ] +matchers: [ foo = bar, dings != bums ] ``` As shown below, in the short-form, it's generally better to quote the list elements to avoid problems with special characters like commas: ```yaml -matchers: [ '{foo="bar",dings!="bums"}' ] +matchers: [ "foo = bar,baz", "dings != bums" ] ``` 3. You can also put both matchers into one PromQL-like string. Single quotes for the whole string work best here. ```yaml -matchers: ['{env=~"produ.*"}', '{baz!~".*quux"}'] +matchers: [ '{foo="bar",dings!="bums"}' ] ``` 4. To avoid any confusion about YAML string quoting and escaping, you can use YAML block quoting and then only worry about the OpenMetrics escaping inside the block. A complex example with a regular expression and different quotes inside the label value is shown below: