Like reads to the disk? No.. I suck at monitoring tbh, I just got a Grafana/Redis setup up this week that monitors the VM. Still trying to figure out how to best monitor everything.

Reply to this note

Please Login to reply.

Discussion

Mostly curious the frequency, types, and shape of all the 'REQ' queries relays get.

Nostr band dev was telling me the read ratios were like 10k read requests for every write.

Would be cool to have data on this, did he mention how he got it? Is there a relay implementation that has support for tracking this?

He has a closed source C++ relay impl he developed. I'm not sure how he's collecting them.

I'd be surprised if no one has a relay with this kind of metric tracking yet. Hmmm

Just keep in mind subscription event result reads can be easily faked/spammed too.

You mean receiving a bunch of pointless/extra/wasteful reads? Seems like something worthy of tracking

I’m sure you can get some insights out of it for operations. Can even help with database optimisations around partitioning, indexes, etc.

However, if your looking to charge per event impression for example, it’s unreliable as a ‘event has been requested/viewed X times’ metric.

I'm only really interested in the former. Hadn't considered charging *per* read or impression. Seems hard to measure given what you've said.

I mention it mostly because the ‘impression’ metric is largely related to todays advertising business models.

At some point someone is going to want to try tracking impressions or a derivative and charging - ideally it’s unworkable and fails. Advertising is a burden on society.

And certainly Nostr will always be read biased. More likely 100-10000x as it grows.

I've been running nostr-rs-relay since the very start but it doesn't have support for data collection/analysis AFAIKø

What kind of stuff are you looking to analyse?

You can use rust with Prometheus crate to collect data for Grafana which is cool.

I’m slowly adding more operational metrics, mostly to understand scaling, growth and performance. And monitor/detect malicious actors.

> Mostly curious the frequency, types, and shape of all the 'REQ' queries relays get.

>

> Nostr band dev was telling me the read ratios were like 10k read requests for every write.

I'm not too sure actually on specific metrics but anything that would give me insights into what is going on so that I can react and improve.

Thanks! I wonder what the best way to approach query stats are. Naive thing would just be to record all queries then analyze periodically.