just see reply - great to hear Thanks - so demo relay not yet attacked !
think ur current BUILT-IN metrics is good enough - maybe add something critical like spam alert
grafana + postgresql should be OPTIONAL for advance admins they install those separately but relaydb should have necessary tables
prometheus not sure what extra advantage it has as data source since can do visualization using postgresql as data-source also
Spam are a headache, and I haven't come up with a particularly good solution yet.
The advance admins indeed require more detailed metrics. This feature is in the planning phase. 🚀
Cool - feel free to look below - for advance Noise/Spam/Attacks there no fixed rule or code - its done based on after identification - anyway to limit ? max_message_length = 5120 and max_event_time_older_than_now = 94608000 like this - ref - code.pobblelabs.org/fossil/nostr_relay/doc/tip/docs/dynamic_lists.md and github.com/rnostr/rnostr/blob/main/rnostr.example.toml
The way nostr_relay sets up whitelists and blacklists through filters is cool, and I'm thinking of adding this feature. If you want to set some basic limitations now, you can check if there's what you want in https://github.com/CodyTseng/nostr-relay-nestjs/blob/master/example.env. Actually, I think the best way to resist spam is POW, but most clients don't support it.
that will nice - so far my test nestjs all good overall - few times hammering it nostr-rs-bench caused some issue in system - unless someone banging it garbage high frequency txt payload - thats kind need to stop or discarded
Thank you very much for your feedback. I'll take some time to test with nostr-rs-bench to what the issue is.
POW is nice - will test - also what 2 means ?
# Optional: Upper limit for created_at field (default: )
# CREATED_AT_UPPER_LIMIT=
# Optional: Lower limit for created_at field (default: )
# CREATED_AT_LOWER_LIMIT=
They are event.created_at limitations. https://github.com/nostr-protocol/nips/pull/897
