From 665a586553f9d63b95780bf444553828439a08be Mon Sep 17 00:00:00 2001
From: tigattack <10629864+tigattack@users.noreply.github.com>
Date: Wed, 27 Nov 2024 03:18:17 +0000
Subject: [PATCH] docs(readme): fix NUT variables docs link

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 06dbeed..2879e16 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@ A sample [dashboard](dashboard/dashboard.json) for Grafana is also available
 ## Variables and information
 The variables exposed to a NUT client by the NUT system are the lifeblood of a deployment. These variables are consumed by this exporter and coaxed to Prometheus types.
 
- * See the [NUT documentation](https://networkupstools.org/docs/user-manual.chunked/apcs01.html) for a list of all possible variables
+ * See the [NUT documentation](https://networkupstools.org/docs/user-manual.chunked/_variables.html) for a list of all possible variables
  * Variables are set as prometheus metrics with the `ups` name added as a lable. Example: `ups.load` is set as `network_ups_tools_ups_load 100`
  * The exporter SHOULD be called with the ups to scrape set in the query string. Example: `https://127.0.0.1:9199/ups_metrics?ups=foo`
  * If the exporter scrapes NUT and detects more than one UPS, it is an error condition that will fail the scrape. In this case, use a variant of the scrape config example below for your environment