Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notify Relay Operator if Relay is Down [Feature Request] #394

Open
alltheseas opened this issue Feb 12, 2023 · 9 comments
Open

Notify Relay Operator if Relay is Down [Feature Request] #394

alltheseas opened this issue Feb 12, 2023 · 9 comments
Labels
enhancement New feature or request legacy for legacy issues

Comments

@alltheseas
Copy link

alltheseas commented Feb 12, 2023

Is your feature request related to a problem? Please describe.
As relay operator, I may not have an easy to way to be notified when my relay goes down.

Describe the solution you'd like

User Story

As a relay operator who is managing my relay in a competitive environment and wants to minimize downtime, I want to receive immediate notifications when my relay goes down, so that I can investigate, take action, and restore my relay.

Acceptance Criteria

  1. Relay operator can opt in to receive notification if nostr.watch detects relay is down
  2. If relay operator opts in, they must provide their npub
  3. Notification sent via DM to relay operator npub over nostr

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
-is this an API call/a webhook?
-is it an email, or npub note? npub DM
-how does relay operator opt in
-future: would it make sense to charge for this service? how might nostr.watch charge for this service?

@dskvr dskvr added the enhancement New feature or request label Feb 12, 2023
@dskvr
Copy link
Collaborator

dskvr commented Feb 12, 2023

A private message on nostr makes sense.

@alltheseas
Copy link
Author

alltheseas commented Feb 12, 2023 via email

@dskvr
Copy link
Collaborator

dskvr commented Feb 13, 2023

There could be a free version that checks (and therefor notifies) less frequently, and a paid option, that checks/notifies within a minute or so.

@dskvr
Copy link
Collaborator

dskvr commented Feb 13, 2023

Additionally, paid version could have other notification options:

  1. High ping notification
  2. NIP-11 modification notification
  3. payments_url 404 notification
    etc.."

@alltheseas
Copy link
Author

alltheseas commented Feb 20, 2023

NIP-11 modification notification

Why should the owner (or manager) of the relay be operated to NIP-11 modification? I am assuming they are the only ones to make NIP-11 changes, and would therefore know about these changes.

High ping notification
payments_url 404 notification

These are great adds

@dskvr
Copy link
Collaborator

dskvr commented Feb 20, 2023

Why should the owner (or manager) of the relay be operated to NIP-11 modification? I am assuming they are the only ones to make NIP-11 changes, and would therefore know about these changes.

Security. "Wait, I didn't change my NIP-11..."

@alltheseas
Copy link
Author

alltheseas commented Feb 20, 2023 via email

@dskvr
Copy link
Collaborator

dskvr commented Feb 22, 2023

Yes, there could be server configuration changes, DNS changes, etc, but there are already services that do this, and most sysadmins will have server and network monitoring tools.

There could also be spikes in events, either positive or negative. Presently not tracking number of events/users on relays, but that will change.

@dskvr dskvr added the legacy for legacy issues label Nov 13, 2023
@dskvr dskvr closed this as completed Nov 23, 2023
@dskvr dskvr reopened this Jan 16, 2024
@alltheseas
Copy link
Author

👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request legacy for legacy issues
Projects
None yet
Development

No branches or pull requests

2 participants