VictoriaMetrics/app
Nikolay Khramchikhin 80a9dc79fe changed vmalert behaviour (#738)
* VMAlert start with empty rules dir

There are some applications (operator for instance), that generates alerts configuration at runtime
and vmalert must start correctly without rules to support this behaviour.
Later application will add rules files and send SIGHUP to vmalert,
which will trigger reading rules files and start rules exectuion.

Removing rules files with SIGHUP signal must stop rules execution and
vmalert will wait for new rules.

* imports sorted

* added test cases for empty rules, removed blank line

* fixed imports conflict

* updated tests
2020-09-03 11:07:40 +03:00
..
vmagent app/{vminsert,vmagent}: allow adding extra labels when importing data via Prometheus, CSV and JSON line formats 2020-09-02 19:47:02 +03:00
vmalert changed vmalert behaviour (#738) 2020-09-03 11:07:40 +03:00
vmauth all: support %{ENV_VAR} placeholders in yaml configs in all the vm* components 2020-08-13 17:17:06 +03:00
vmbackup all: allow using KB, MB, GB, KiB, MiB and GiB suffixes in command-line flag values related to byte sizes or byte rates 2020-08-16 17:08:28 +03:00
vminsert app/{vminsert,vmagent}: allow adding extra labels when importing data via Prometheus, CSV and JSON line formats 2020-09-02 19:47:02 +03:00
vmrestore all: allow using KB, MB, GB, KiB, MiB and GiB suffixes in command-line flag values related to byte sizes or byte rates 2020-08-16 17:08:28 +03:00
vmselect all: allow using KB, MB, GB, KiB, MiB and GiB suffixes in command-line flag values related to byte sizes or byte rates 2020-08-16 17:08:28 +03:00
vmstorage app: respect CPU limits set via cgroups 2020-08-11 23:01:03 +03:00