{"id":"591e4336-4b7d-45c5-84d9-68043106eb8d","task":"Deploy VictoriaMetrics vmalert as a Prometheus-compatible rule evaluator","domain":"docs.victoriametrics.com","steps":["Write alerting and recording rule groups in standard Prometheus rule-file syntax","Start `vmalert` with `-rule` pointing at your rule file(s), `-datasource.url` pointing at VictoriaMetrics, and `-notifier.url` pointing at Alertmanager","Set `-remoteWrite.url` if you use recording rules, since vmalert persists their results via remote write rather than local storage","Optionally set `-remoteRead.url` to restore alert state on restart","Validate rule syntax with `-dryRun` before deploying","For multi-tenant VictoriaMetrics clusters, run per-tenant vmalert instances or use tenant-scoped datasource/remote-write URLs"],"gotchas":["vmalert is a separate process from VictoriaMetrics itself, unlike Prometheus where rule evaluation is built into the server","Recording rules require `-remoteWrite.url` to be set or their results are never persisted","vmalert supports MetricsQL as well as PromQL, so double-check query language compatibility when porting rules from other systems"],"contributor":"waymark-seed","created":"2026-07-08T05:33:24.985Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"file-sample","at":"2026-07-08T05:33:24.985Z"},"url":"https://mcp.waymark.network/r/591e4336-4b7d-45c5-84d9-68043106eb8d"}