summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Akritidis <43294513+cakrit@users.noreply.github.com>2023-02-08 04:59:59 -0800
committerGitHub <noreply@github.com>2023-02-08 04:59:59 -0800
commit255a821dac29b7ccfb205b84e5c699ae9b103012 (patch)
tree35e39286dfda3885735bc67c8ff8fe123300e362
parent738e4f10bcc164ef1515901f4e261eee3e9bc88b (diff)
Add export for people running their own registry (#14457)
See https://github.com/netdata/netdata/issues/3495#issuecomment-1408452259
-rw-r--r--health/notifications/README.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/health/notifications/README.md b/health/notifications/README.md
index c59feccedb..45f56dc356 100644
--- a/health/notifications/README.md
+++ b/health/notifications/README.md
@@ -78,6 +78,8 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
/usr/libexec/netdata/plugins.d/alarm-notify.sh test "ROLE"
```
+If you are [running your own registry](https://github.com/netdata/netdata/blob/master/registry/README.md#run-your-own-registry), add `export NETDATA_REGISTRY_URL=[YOUR_URL]` before calling `alarm-notify.sh`.
+
Note that in versions before 1.16, the plugins.d directory may be installed in a different location in certain OSs (e.g. under `/usr/lib/netdata`). You can always find the location of the alarm-notify.sh script in `netdata.conf`.
If you need to dig even deeper, you can trace the execution with `bash -x`. Note that in test mode, alarm-notify.sh calls itself with many more arguments. So first do