Roman Khavronenko 48fb972ddc vmalert: make notifier.Addr optional (#1870) ... For a long time notifier.Addr flag was required. The assumption was that vmalert will be always used for alerting. However, practice shows that some users need only recording rules. In this case, requirement of notifier.Addr is ambigious. The change verifies if loaded config contains recording or alerting rules and if there are corresponding flags set. This is true for initial config load and hot reload. Signed-off-by: hagen1778 <roman@victoriametrics.com>		2021-11-30 01:23:00 +02:00
..
alert.go	vmalert: correctly calculate alert ID including extra labels (#1734)	2021-10-22 12:31:35 +03:00
alert_test.go	vmalert: support rules backfilling (aka replay) (#1358)	2021-06-09 12:30:54 +03:00
alertmanager.go	all: consistently return application/json content-type without charset=utf-8	2021-11-09 18:07:22 +02:00
alertmanager_request.qtpl	Support of custom URL path for alert (#560)	2020-06-21 16:33:58 +03:00
alertmanager_request.qtpl.go	Support of custom URL path for alert (#560)	2020-06-21 16:33:58 +03:00
alertmanager_test.go	Vmalert metrics update (#1580)	2021-09-01 12:19:34 +03:00
init.go	vmalert: make notifier.Addr optional (#1870)	2021-11-30 01:23:00 +02:00
notifier.go	Vmalert metrics update (#1580)	2021-09-01 12:19:34 +03:00
package_test.go	Support of custom URL path for alert (#560)	2020-06-21 16:33:58 +03:00
template_func.go	vmalert: support rules backfilling (aka replay) (#1358)	2021-06-09 12:30:54 +03:00