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
Copy file name to clipboardExpand all lines: charts/grafana/README.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,11 @@ to `global.imageRegistry`. If you were not previously setting `global.image.regi
53
53
is required on upgrade. If you were previously setting `global.image.registry`, you will
54
54
need to instead set `global.imageRegistry`.
55
55
56
+
### To 10.0.0
57
+
58
+
Static alerting resources now support Helm templating. If you are using the `alerting` configuration,
59
+
double curly braces must be escaped using `{{ "{{" }}` syntax to prevent unintended template processing.
60
+
56
61
## Configuration
57
62
58
63
| Parameter | Description | Default |
@@ -681,7 +686,7 @@ The two possibilities for static alerting resource provisioning are:
681
686
* The format of the files is defined in the [Grafana documentation](https://grafana.com/docs/grafana/next/alerting/set-up/provision-alerting-resources/file-provisioning/) on file provisioning.
682
687
* The chart supports importing YAML and JSON files.
683
688
* The filename must be unique, otherwise one volume mount will overwrite the other.
684
-
* In case of inlining, double curly braces that arise from the Grafana configuration format and are not intended as templates for the chart must be escaped.
689
+
* Alerting configurations support Helm templating. Double curly braces that arise from the Grafana configuration format and are not intended as templates for the chart must be escaped.
685
690
* The number of total files under `alerting:` is not limited. Each file will end up as a volume mount in the corresponding provisioning folder of the deployed Grafana instance.
686
691
* The file size for each import is limited by what the function `.Files.Get` can handle, which suffices for most cases.
0 commit comments