aboutsummaryrefslogtreecommitdiffstats
path: root/netwatch-notify.rsc
AgeCommit message (Collapse)AuthorFilesLines
2024-02-28netwatch-notify: work around race conditionGravatar Christian Hesse1-8/+12
This used to crash every now and then with: > script;error script error: no such item (4) I guess this is caused by querying the dns cache just exactly when a record expires. The chance is maximized: The script is started by scheduler every minute, and the record's ttl is a multiple of a minute. Let's query records that are not about to expire immediately, and try again.
2024-02-28netwatch-notify: restore the check 🥴Gravatar Christian Hesse1-1/+2
This reverts commit 28da1da49e275fef6089a103edf6c158bbff317f. Chances are that we have to resolve a CNAME, that does not match when querying the cache. How to handle CNAME do multiple A records? 🤨
2024-02-28netwatch-notify: simplify the checkGravatar Christian Hesse1-2/+1
2024-02-28netwatch-notify: ... and switch state to "unknown" on host updateGravatar Christian Hesse1-0/+1
2024-02-28netwatch-notify: handle status "down" in its own condition...Gravatar Christian Hesse1-1/+4
... instead of else-branch. This makes sure to skip hosts that just became "unknown". (Possible soon!)
2024-02-28netwatch-notify: use logical operator, no literal "and"Gravatar Christian Hesse1-1/+1
Just like we do everywhere else.
2024-02-19netwatch-notify: do not update with record in cacheGravatar Christian Hesse1-1/+2
Using `:resolve` we have just one address, but chances are several records do exist. These end up in cache, so we are happy to find them there - no need to update then.
2024-01-30netwatch-notify: use :jobname to get script nameGravatar Christian Hesse1-1/+3
2024-01-01update copyright for 2024Gravatar Christian Hesse1-1/+1
2023-10-27netwatch-notify: match on word boundaryGravatar Christian Hesse1-1/+1
2023-09-29netwatch-notify: allow to give different origin for hosts...Gravatar Christian Hesse1-6/+4
... to use differing notification settings. Add an origin name in netwatch configuration: /tool/netwatch/add comment="notify, name=dns-google, origin=netwatch-notify-google" address=8.8.8.8; /tool/netwatch/add comment="notify, name=dns-cloudflare, origin=netwatch-notify-cloudflare" address=1.1.1.1; Then configure the notification settings in `global-config-overlay`: :global EmailGeneralToOverride { "netwatch-notify-google"="google@example.com"; "netwatch-notify-cloudflare"="cloudflare@example.com"; } I think it is best to handle this as a hidden setting... Handle with care!
2023-08-18netwatch-notify: drop RouterOS version dependencyGravatar Christian Hesse1-2/+0
... as global-functions depend on RouterOS 7.9beta already.
2023-06-28netwatch-notify: drop the delay on startup...routeros-7.9beta4-6Gravatar Christian Hesse1-4/+2
... now that in RouterOS 7.9 netwatch itself comes with a startup-delay. Hosts in state 'unknown' are just ignored.
2023-05-31netwatch-notify: ignore status 'unknown'Gravatar Christian Hesse1-1/+1
2023-03-20netwatch-notify: support note in notificationchange-96Gravatar Christian Hesse1-0/+6
2023-03-07rename scripts and add file extension ".rsc"change-95Gravatar Christian Hesse1-0/+186
No functional change for the user... The migration is done automatically.