Step by step enriching my #relay monitoring dashboard for #nostr :
Présent !
Mais c'est vrai que ça s'est calmé du côté du #nostrfr ces derniers temps. La première vague de "hype" terminée ?
Il se dit que les méchants ils sont pas gentils et que ça, c'est pas très très bien
😱😓
Si vous ne connaissez pas ce réal', je vous conseille de voir son film "la vache", très bien filmé, drôle et touchant.
,,#nostrfr
GM #nostrfr !
I'll start checking for data monitoring regarding NIP-57 ( zaps ). However as far as I've checked yet, I'll have the same difficulties I have with NIP-56 data ( reports ).
I guess I'll have to switch to postures and/or use another service ( maybe influxdb ? ) to get proper data
#relay #monitoring #nostr
The key is to play with subqueries and event kinds
Erratum : the user data is not stored on a specific table, thus the relay records metadata events. I cross the data when possible, same way
The relay provides a table for users that broadcast metadata update on the relay.
What I did is to fetch the username if the npub did an update of the metadata on the relay, otherwise the pubkey of the user is displayed as hex.
#NIP-56 on #grafana :
I currently find many limitations to monitor the NIP-56 content :
- The tag data store structure in the event table is cumbersome to manipulate and the tag table does not provide the NIP-56 tags itself.
- There are different types of report with different data structures to handle
with CASE WHEN instructions in query.
- The events tags can be declared in any order making it difficult with SQLite to filter out the Json content.
- Grafana does not provide hex to bech32 transformations
Those limitations lead me for now to a probably too complex query with small readibility :
https://gist.github.com/Asone/0b89b834e0aba30a54c61927425b8f25
It provides, however, a tool for reporting and moderation, and a base to build other metrics around NIP-56 tags and 1984 event kind.
I am wondering though if it wouldn't be easier to provide monitoring for that kind of the reported content on #relays with postures.
Also I'd like to check how to extract raw logs for monitoring.
#nostr #relay #monitoring
#NIP-56 on #grafana :
I currently find many limitations to monitor the NIP-56 content :
- The tag data store structure in the event table is cumbersome to manipulate and the tag table does not provide the NIP-56 tags itself.
- There are different types of report with different data structures to handle
with CASE WHEN instructions in query.
- The events tags can be declared in any order making it difficult with SQLite to filter out the Json content.
- Grafana does not provide hex to bech32 transformations
Those limitations lead me for now to a probably too complex query with small readibility :
https://gist.github.com/Asone/0b89b834e0aba30a54c61927425b8f25
It provides, however, a tool for reporting and moderation, and a base to build other metrics around NIP-56 tags and 1984 event kind.
Btw, I'll also update the dashboard gist I shared the other day, as I fine-tuned some other metrics widgets
Ok, first draft of a grafana widget to have an overview of the NIP-56 events almost ready.
I will share it in the next 24h, but there's plenty of things to say about it as i had to dig quite a bit to get the relevant information.
#monitoring #relay #nostr
Nope, I'm using nostr-rs-relay