This is a monitoring agent that can monitor websocket latency to nostr relays.
It can publish the results to InfluxDB and to nostr relays using NIP66
Download the latest relase from the releases page
Create an env file named .monitorlizard.env in the current directory. Example contents of .monitorlizard.env:
# INFLUXDB IS OPTIONAL NO NEED TO SET THESE
INFLUXDB_URL=
INFLUXDB_TOKEN=
INFLUXDB_ORG=
INFLUXDB_BUCKET=
INFLUXDB_MEASUREMENT=
# Name of your monitor
MONITOR_NAME=mylizard
# Publish metrics to nostr relays
# Recommend generating a new nostr keypair for this monitor.
NOSTR_PUBLISH=true
NOSTR_PRIVATE_KEY=(hex)
# Where to publish events.
# This can be a comma separated list if you want to publish to multiple relays.
NOSTR_PUBLISH_RELAY_METRICS=wss://monitorlizard.nostr1.com
NOSTR_PUBLISH_MONITOR_PROFILE=true
MONITOR_COUNTRY_CODE=US
MONITOR_ABOUT=Relay Monitor new Lizard
# Frequency to run and publish checks.
MONITOR_FREQUENCY=60
# optional specify one or more relays (or use command line option)
RELAY_URLS=wss://myrelay1.com,wss://myrelay2.com
# optionally tag relay types (NIP-66 T tag); chain several with ;
# RELAY_URLS=wss://myrelay1.com;PublicOutbox;Community,wss://myrelay2.com;Search
# monitorlizard geoencodes this for you and encodes to a low
# precision (general area or country)
# the lat, long of the monitor location
MONITOR_LATITUDE=47.620564
MONITOR_LONGITUDE=-122.350616
# this is the lat,long of the relay(s) location
RELAY_LATITUDE=43.000000
RELAY_LONGITUDE=-75.000000
Run it!
./monitorlizard wss://myrelay.example.com
cp example.monitorlizard.env .monitorlizard.env
# Edit the settings to match your needs.
go build
./monitorlizard wss://myrelay.example.com