Hey all,
I've mentioned this too many times in the past, but I'm finally able to push out the first iteration of my LND Lightning Dashboard project for feedback. It's very much a PoC to deploy a self-hosted docker Grafana, Prometheus, Loki stack to monitor and have a SPoG on your LND/LNDg setup.
This project will be published on GitHub in the next week or two. I'm currently sitting on the setup I have launched to feed in more data to check stability before the source goes public.
I would appreciate any feedback or requests people have on types of data they'd like to see visualized - whether from another location or currently not available.
https://docs.google.com/document/d/1SDfBKnJxaPmByGY4er9feJ59HgNN4kQJGwtZ86Cx7b4/edit?usp=sharing
I'll be reading these replies if you'd prefer to post here rather than anonymously in the google doc
Thank You!
-Auth
Hi! Nice to see your project.
I started a similar project some years ago and abandoned it.
But the idea is similar or even more advanced than yours. Perhaps you are interested in continuing it. If you are, have a look and msg me.
https://github.com/JaviLib/LNBank
Note: I am a real programmer, so I can help you when I have time.
Adding it on my list to delve into! I think your project is a bit more integrated, judging from the readme, than what I'm building, as my goal is purely monitoring.
I'll be posting again once I publish my code on GH, and will happily take any assistance or insights you can provide, beyond me gleaning from your repo!
Mine is also for monitoring, it launches LNDg and LNBits, along with LND and Core, of course. When it is finished, it can filter logs by type and app, and maintain a full history.
Interesting.
I like the part showing the HTLCs visualizer. Focus more on that part. A serious LN node operator will always want to see why some HTLCs fail and find solutions.
Ya! It's a cool little thing... I have it in my TODO to allow HTLC replay. Otherwise an average node runner may see 1 dot move every 15-60 minutes.
Glad you like it :)
I am glad somebody is doing this.
LN node runners, especially noobs need these kind of detailed dashboards to give the best overview and take the right decisions for a better PUBLIC routing.
I think a lot of node runners still don't know the big difference between a public and private node. And we end up with shity public nodes that in fact should be private nodes.
I've seen a lot this misconception that in order to be able to make a payment over LN you need to run a public node. Wrong. Totally wrong.
Maybe you can also add a section for LSPs? Or managing private channels ?
A LSP have a very difficult task, dealing with public and private channels.
I think what you're looking for is out of scope for my intention. My goal is to just help provide monitoring frameworks for people who want to run public nodes.
LSP integration could be a facet of it that I didn't consider, so that's now on my list of things to think about. I frankly do not have much insight into private channel management / payment node management. Hopefully yourself and others will be able to provide insight and feature requests as this project matures.
My ideal would be a TUI that works over ssh. That is, so I can view the dashboard with only ssh access to the node.
To clarify - as in -
Port forwarding in to view Grafana?
Dashboard exports reports in HTML/PDF/etc?
Dashboard be rendered in a Terminal view (similar to HTOP?)?
I'm not sure how it'd work exactly, but I've been wishing for an lnd tui since this post: #399987
This sounds really cool. I have been playing around a lot with LNDg lately. Specifically, can it provide a liitle more certainty about potential auto rebalance costs and whether they make economic sense? What about failed HTLCs? Could we get insight beyond that shown on LNDg, (we can see chan in and out and insufficient balance now) or would it just provide an easier way to visualize the information?
This tool isn't meant to directly provide feedback into configuring rebalancing as that is currently out of scope, as that goes past Monitoring into Actionable Analytics.
Failed HTLC's are in scope to a degree... I've noted down your thought to see if that's a thread I can progress on. As a reminder, there's limited amounts of knowledge on HTLC's that your node is routing, which is one of the privacy features of Lightning.
Only for this you got my respect :)