Merge pull request #191552 from trask/regexp-clarification

Regexp clarification

Author: PRMerger13

articles/azure-monitor/app/java-standalone-sampling-overrides.md

@@ -69,6 +69,9 @@ To begin, create a configuration file named *applicationinsights.json*. Save it
 When a span is started, the attributes present on the span at that time are used to check if any of the sampling
 overrides match.
 
+Matches can be either `strict` or `regexp`. Regular expression matches are performed against the entire attribute value,
+so if you want to match a value that contains `abc` anywhere in it, then you need to use `.*abc.*`.
+
 If one of the sampling overrides match, then its sampling percentage is used to decide whether to sample the span or
 not.
 

articles/azure-monitor/app/java-standalone-telemetry-processors.md

@@ -236,7 +236,9 @@ To configure this option, under `include` or `exclude` (or both), specify at lea
 The include-exclude configuration allows more than one specified condition.
 All specified conditions must evaluate to true to result in a match. 
 
-* **Required field**: `matchType` controls how items in `spanNames` arrays and `attributes` arrays are interpreted. Possible values are `regexp` and `strict`. 
+* **Required field**: `matchType` controls how items in `spanNames` arrays and `attributes` arrays are interpreted.
+  Possible values are `regexp` and `strict`. Regular expression matches are performed against the entire attribute value,
+  so if you want to match a value that contains `abc` anywhere in it, then you need to use `.*abc.*`.
 
 * **Optional fields**: 
     * `spanNames` must match at least one of the items. 
@@ -383,7 +385,9 @@ To configure this option, under `include` or `exclude` (or both), specify at lea
 The include-exclude configuration allows more than one specified condition.
 All specified conditions must evaluate to true to result in a match. 
 
-* **Required field**: `matchType` controls how items in `spanNames` arrays and `attributes` arrays are interpreted. Possible values are `regexp` and `strict`. 
+* **Required field**: `matchType` controls how items in `spanNames` arrays and `attributes` arrays are interpreted.
+  Possible values are `regexp` and `strict`. Regular expression matches are performed against the entire attribute value,
+  so if you want to match a value that contains `abc` anywhere in it, then you need to use `.*abc.*`.
 
 * **Optional fields**: 
     * `spanNames` must match at least one of the items. 
@@ -506,7 +510,9 @@ The include-exclude configuration allows more than one specified condition.
 All specified conditions must evaluate to true to result in a match. 
 
 * **Required field**: 
-  * `matchType` controls how items in `attributes` arrays are interpreted. Possible values are `regexp` and `strict`. 
+  * `matchType` controls how items in `attributes` arrays are interpreted. Possible values are `regexp` and `strict`.
+     Regular expression matches are performed against the entire attribute value,
+     so if you want to match a value that contains `abc` anywhere in it, then you need to use `.*abc.*`.
   * `attributes` specifies the list of attributes to match. All of these attributes must match exactly to result in a match.
 
 > [!NOTE]
@@ -566,7 +572,9 @@ To configure this option, under `exclude`, specify the `matchType` one or more `
 
 * **Required field**:
   * `matchType` controls how items in `metricNames` are matched. Possible values are `regexp` and `strict`.
-  * `metricNames` must match at least one of the items.
+     Regular expression matches are performed against the entire attribute value,
+     so if you want to match a value that contains `abc` anywhere in it, then you need to use `.*abc.*`.
+   * `metricNames` must match at least one of the items.
 
 ### Sample usage