pull down to refresh

5 sats \ 3 replies \ @supratic OP 21 Aug \ parent \ on: Authenticity · Lightning Transactions Live Flow & Node Health Visualization Design lightning

Legend, thank you for putting this together. It's great to observe a live node. We can wait for the node health. Where are you getting the data from? Or are you calculating it with this tool?

write
compose
5 sats \ 2 replies \ @AuthenticityBTC 21 Aug

I wrote coughClaudecough a custom setup for this, roughly as follows

  1. Go gRPC / HTLC interceptor with a readonly macaroon that grabs all the data and then parses out the things I want the Visualizer to see. It then sanitizes things and pushes it as a feed.json (events) and ring.json (anonymized channels) files to Amazon S3
  2. Amazon S3 holds only the latest copy of this, and versions it out automatically
  3. A web frontend built on HTML/JS and hosted as an S3 Static Website
  4. The actual Visualizer just pulls the updated JSOn files and presents it.

It is on my list to push to Github. Drowning in higher priority life stuff and getting things pushed to OpenSource keeps dropping down the list (my dashboard project/idea, this visualizer, node temperature metrics, network temperature metrics, etc)

reply
5 sats \ 1 reply \ @supratic OP 21 Aug

is it worth hosting the data in S3? Could the whole process be handled easily with GH actions and perhaps storing the json as gist instead?

reply
5 sats \ 0 replies \ @AuthenticityBTC 21 Aug

Currently I update the feed every 15s. There's a ton of ways to do this, including gist.

I just went what's simplest and easiest to me. I run on AWS to begin with so I keep everything I can there.

reply