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: docs/configuration.md
+5-4
Original file line number
Diff line number
Diff line change
@@ -487,7 +487,7 @@ You can use this mode if you suspect there is an issue with fallback mode or UTF
487
487
488
488
You can use `amtool` to validate that an Alertmanager configuration file is compatible with UTF-8 strict mode before enabling it in Alertmanager server. You do not need a running Alertmanager server to do this.
489
489
490
-
Just like Alertmanager server, `amtool` will log a warning if the configuration is incompatible or contains disagreement:
490
+
Just like Alertmanager server, `amtool` will log a warning if the configuration is incompatible or contains disagreement:
491
491
492
492
```
493
493
amtool check-config config.yml
@@ -503,7 +503,7 @@ Found:
503
503
- 0 templates
504
504
```
505
505
506
-
You will know if a configuration is compatible with UTF-8 strict mode when no warnings are logged in `amtool`:
506
+
You will know if a configuration is compatible with UTF-8 strict mode when no warnings are logged in `amtool`:
507
507
508
508
```
509
509
amtool check-config config.yml
@@ -644,7 +644,7 @@ Here are some more examples:
644
644
```
645
645
646
646
As shown below, in the short-form, it's better to use double quotes to avoid problems with special characters like commas:
0 commit comments