You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specify whether index patterns should include a wildcard (*) when creating an index template. This is particularly useful to prevent errors in scenarios where index templates are generated automatically, and multiple services with distinct suffixes are in use.
1567
+
1568
+
Default value is `true`.
1569
+
1570
+
Consider the following JSON error response when index patterns clash due to wildcard usage:
1571
+
```json
1572
+
{
1573
+
"error": {
1574
+
"root_cause": [
1575
+
{
1576
+
"type": "illegal_argument_exception",
1577
+
"reason": "index template [eks-kube-apiserver] has index patterns [eks-kube-apiserver*] matching patterns from existing templates [eks-kube-apiserver-audit] with patterns (eks-kube-apiserver-audit => [eks-kube-apiserver-audit*]) that have the same priority [0], multiple index templates may not match during index creation, please use a different priority"
1578
+
}
1579
+
],
1580
+
"type": "illegal_argument_exception",
1581
+
"reason": "index template [eks-kube-apiserver] has index patterns [eks-kube-apiserver*] matching patterns from existing templates [eks-kube-apiserver-audit] with patterns (eks-kube-apiserver-audit => [eks-kube-apiserver-audit*]) that have the same priority [0], multiple index templates may not match during index creation, please use a different priority"
1582
+
},
1583
+
"status": 400
1584
+
}
1585
+
```
1586
+
1587
+
#### Usage Examples
1588
+
1589
+
When `data_stream_template_use_index_patterns_wildcard` is set to `true` (default):
0 commit comments