Kiu/VictoriaMetrics
Kiu/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-12-15 08:23:34 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
bb26aa9b1f
VictoriaMetrics/app/vmalert/Makefile

111 lines
2.9 KiB
Makefile
Raw Normal View History

app/vmalert: sync with master branch
2020-04-27 23:19:27 +02:00
# All these commands must run from repository root.
vmalert: add initial UI implementation (#1602) New UI pages: / - welcome page with API handlers list; /groups - list of all rules per group; /alerts - list of all active alerts; /groupID/alertID/status - status of the active alert;
2021-09-07 21:39:22 +02:00
templates-gen: install-qtc
qtc -dir=./app/vmalert
vmalert: templates-gen
app/vmalert: sync with master branch
2020-04-27 23:19:27 +02:00
APP_NAME=vmalert $(MAKE) app-local
vmalert-race:
APP_NAME=vmalert RACE=-race $(MAKE) app-local
vmalert-prod:
APP_NAME=vmalert $(MAKE) app-via-docker
vmalert-pure-prod:
APP_NAME=vmalert $(MAKE) app-via-docker-pure
vmalert-amd64-prod:
APP_NAME=vmalert $(MAKE) app-via-docker-amd64
vmalert-arm-prod:
APP_NAME=vmalert $(MAKE) app-via-docker-arm
vmalert-arm64-prod:
APP_NAME=vmalert $(MAKE) app-via-docker-arm64
vmalert-ppc64le-prod:
APP_NAME=vmalert $(MAKE) app-via-docker-ppc64le
vmalert-386-prod:
APP_NAME=vmalert $(MAKE) app-via-docker-386
package-vmalert:
APP_NAME=vmalert $(MAKE) package-via-docker
package-vmalert-pure:
APP_NAME=vmalert $(MAKE) package-via-docker-pure
package-vmalert-amd64:
APP_NAME=vmalert $(MAKE) package-via-docker-amd64
package-vmalert-arm:
APP_NAME=vmalert $(MAKE) package-via-docker-arm
package-vmalert-arm64:
APP_NAME=vmalert $(MAKE) package-via-docker-arm64
package-vmalert-ppc64le:
APP_NAME=vmalert $(MAKE) package-via-docker-ppc64le
package-vmalert-386:
APP_NAME=vmalert $(MAKE) package-via-docker-386
publish-vmalert:
APP_NAME=vmalert $(MAKE) publish-via-docker
test-vmalert:
vmalert: fix potential race during configuration reloads (#497) Configuration reload and rules evaluation can't be executed in same time now. This may make reload time longer but prevents from potential races.
2020-05-17 16:12:09 +02:00
go test -v -race -cover ./app/vmalert -loggerLevel=ERROR
go test -v -race -cover ./app/vmalert/datasource
go test -v -race -cover ./app/vmalert/notifier
vmalert: Add recording rules support. (#519) * vmalert: Add recording rules support. Recording rules support required additional service refactoring since it wasn't planned to support them from the very beginning. The list of changes is following: * new entity RecordingRule was added for writing results of MetricsQL expressions into remote storage; * interface Rule now unites both recording and alerting rules; * configuration parser was moved to separate package and now performs more strict validation; * new endpoint for listing all groups and rules in json format was added; * evaluation interval may be set to every particular group; * vmalert: uncomment tests * vmalert: rm outdated TODO * vmalert: fix typos in README
2020-06-01 12:46:37 +02:00
go test -v -race -cover ./app/vmalert/config
Vmalert metrics update (#1580) * vmalert: remove `vmalert_execution_duration_seconds` metric The summary for `vmalert_execution_duration_seconds` metric gives no additional value comparing to `vmalert_iteration_duration_seconds` metric. * vmalert: update config reload success metric properly Previously, if there was unsuccessfull attempt to reload config and then rollback to previous version - the metric remained set to 0. * vmalert: add Grafana dashboard to overview application metrics * docker: include vmalert target into list for scraping * vmalert: extend notifier metrics with addr label The change adds an `addr` label to metrics for alerts_sent and alerts_send_errors to identify which exact address is having issues. The according change was made to vmalert dashboard. * vmalert: update documentation and docker environment for vmalert's dashboard Mention Grafana's dashboard in vmalert's README in a new section #Monitoring. Update docker-compose env to automatically add vmalert's dashboard. Update docker-compose README with additional info about services.
2021-08-31 11:28:02 +02:00
go test -v -race -cover ./app/vmalert/remotewrite
app/vmalert: sync with master branch
2020-04-27 23:19:27 +02:00
run-vmalert: vmalert
vmalert: Add recording rules support. (#519) * vmalert: Add recording rules support. Recording rules support required additional service refactoring since it wasn't planned to support them from the very beginning. The list of changes is following: * new entity RecordingRule was added for writing results of MetricsQL expressions into remote storage; * interface Rule now unites both recording and alerting rules; * configuration parser was moved to separate package and now performs more strict validation; * new endpoint for listing all groups and rules in json format was added; * evaluation interval may be set to every particular group; * vmalert: uncomment tests * vmalert: rm outdated TODO * vmalert: fix typos in README
2020-06-01 12:46:37 +02:00
./bin/vmalert -rule=app/vmalert/config/testdata/rules2-good.rules \
app/vmalert: restore alerts state from datasource metrics (#461) * app/vmalert: restore alerts state from datasource metrics Vmalert will restore alerts state for rules that have `rule.For` > 0 from previously written timeseries via `remotewrite.url` flag. * app/vmalert: mention remotewerite and remoteread configuration in README
2020-05-04 23:51:22 +02:00
-datasource.url=http://localhost:8428 \
-notifier.url=http://localhost:9093 \
app/vmalert: support multiple notifier urls (#584) (#590) * app/vmalert: support multiple notifier urls (#584) User now can set multiple notifier URLs in the same fashion as for other vmutils (e.g. vmagent). The same is correct for TLS setting for every configured URL. Alerts sending is done in sequential way for respecting the specified URLs order. * app/vmalert: add basicAuth support for notifier client (#585) The change adds possibility to set basicAuth creds for notifier client in the same fasion as for remote write/read and datasource.
2020-06-29 21:21:03 +02:00
-notifier.url=http://127.0.0.1:9093 \
vmalert: fix flag names and description in README (#475) Change also adds the recommendation for `remotewrite` queue error.
2020-05-13 20:32:21 +02:00
-remoteWrite.url=http://localhost:8428 \
-remoteRead.url=http://localhost:8428 \
app/vmalert: support `external.label` to specify global labelset for all rules #622 (#652) `external.label` flag supposed to help to distinguish alert or recording rules source in situations when more than one `vmalert` runs for the same datasource or AlertManager.
2020-07-28 13:20:31 +02:00
-external.label=cluster=east-1 \
-external.label=replica=a \
vmalert: automatically reload configuration on file change (#1326) New flag `-rule.configCheckInterval` defines how often `vmalert` will re-read config file. If it detects any changes, the config will be reloaded. This behaviour is turned off by default. https://github.com/VictoriaMetrics/VictoriaMetrics/issues/512
2021-05-25 15:27:22 +02:00
-evaluationInterval=3s \
-rule.configCheckInterval=10s
app/vmalert: sync with master branch
2020-04-27 23:19:27 +02:00
vmalert: support rules backfilling (aka `replay`) (#1358) * vmalert: support rules backfilling (aka `replay`) vmalert can `replay` configured rules in the past and backfill results via remote write protocol. It supports MetricsQL/PromQL storage as data source, and can backfill data to remote write compatible storage. Supports recording and alerting rules `replay`. See more details in README. https://github.com/VictoriaMetrics/VictoriaMetrics/issues/836 * vmalert: review fixes * vmalert: readme fixes
2021-06-09 11:20:38 +02:00
replay-vmalert: vmalert
./bin/vmalert -rule=app/vmalert/config/testdata/rules-replay-good.rules \
-datasource.url=http://localhost:8428 \
-remoteWrite.url=http://localhost:8428 \
-external.label=cluster=east-1 \
-external.label=replica=a \
-replay.timeFrom=2021-05-11T07:21:43Z \
-replay.timeTo=2021-05-29T18:40:43Z
app/vmalert: sync with master branch
2020-04-27 23:19:27 +02:00
vmalert-amd64:
all: add mssing APP_NAME to vm*-GOARCH builds
2020-07-31 12:42:09 +02:00
CGO_ENABLED=1 GOARCH=amd64 $(MAKE) vmalert-local-with-goarch
app/vmalert: sync with master branch
2020-04-27 23:19:27 +02:00
vmalert-arm:
all: add mssing APP_NAME to vm*-GOARCH builds
2020-07-31 12:42:09 +02:00
CGO_ENABLED=0 GOARCH=arm $(MAKE) vmalert-local-with-goarch
app/vmalert: sync with master branch
2020-04-27 23:19:27 +02:00
vmalert-arm64:
all: add mssing APP_NAME to vm*-GOARCH builds
2020-07-31 12:42:09 +02:00
CGO_ENABLED=0 GOARCH=arm64 $(MAKE) vmalert-local-with-goarch
app/vmalert: sync with master branch
2020-04-27 23:19:27 +02:00
vmalert-ppc64le:
all: add mssing APP_NAME to vm*-GOARCH builds
2020-07-31 12:42:09 +02:00
CGO_ENABLED=0 GOARCH=ppc64le $(MAKE) vmalert-local-with-goarch
app/vmalert: sync with master branch
2020-04-27 23:19:27 +02:00
vmalert-386:
all: add mssing APP_NAME to vm*-GOARCH builds
2020-07-31 12:42:09 +02:00
CGO_ENABLED=0 GOARCH=386 $(MAKE) vmalert-local-with-goarch
vmalert-local-with-goarch:
APP_NAME=vmalert $(MAKE) app-local-with-goarch
app/vmalert: sync with master branch
2020-04-27 23:19:27 +02:00
vmalert-pure:
APP_NAME=vmalert $(MAKE) app-local-pure
Makefile: prepare vmutils-windows-*.zip archive on `make release-vmutils` command The archive contains the following executables for Windows: * vmagent * vmalert * vmauth * vmctl Other components - vmbackup, vmrestore, victoria-metrics - aren't supported for Windows yet
2021-03-16 19:49:07 +01:00
vmalert-windows-amd64:
GOARCH=amd64 APP_NAME=vmalert $(MAKE) app-local-windows-with-goarch
vmalert-windows-amd64-prod:
APP_NAME=vmalert $(MAKE) app-via-docker-windows-amd64
Reference in New Issue Copy Permalink