From 94727f758818675b093ebabdb07305415615feab Mon Sep 17 00:00:00 2001
From: Vika <info@victoriametrics.com>
Date: Thu, 8 Feb 2024 16:49:35 +0000
Subject: [PATCH] update wiki pages

---
 vmagent.md | 2 +-
 vmalert.md | 5 ++---
 2 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/vmagent.md b/vmagent.md
index 6b0680a..1dda7be 100644
--- a/vmagent.md
+++ b/vmagent.md
@@ -126,7 +126,7 @@ additionally to pull-based Prometheus-compatible targets' scraping:
   kill -SIGHUP `pidof vmagent`
   ```
 
-* Sending HTTP request to `http://vmagent:8429/-/reload` endpoint.
+* Sending HTTP request to `http://vmagent:8429/-/reload` endpoint. This endpoint can be protected with `-reloadAuthKey` command-line flag.
 
 There is also `-promscrape.configCheckInterval` command-line option, which can be used for automatic reloading configs from updated `-promscrape.config` file.
 
diff --git a/vmalert.md b/vmalert.md
index cbcdc55..20a88a3 100644
--- a/vmalert.md
+++ b/vmalert.md
@@ -1420,9 +1420,8 @@ The shortlist of configuration flags is the following:
 `vmalert` supports "hot" config reload via the following methods:
 
 * send SIGHUP signal to `vmalert` process;
-* send GET request to `/-/reload` endpoint;
-* configure `-configCheckInterval` flag for periodic reload
-  on config change.
+* send GET request to `/-/reload` endpoint (this endpoint can be protected with `-reloadAuthKey` command-line flag);
+* configure `-configCheckInterval` flag for periodic reload on config change.
 
 ### URL params