lightninglabs / lightninglabs/lndmon

Extended Routing Dashboard

Open
#62 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
160
Forks
53
PR merge metrics
No merged PRs in 30d

Description

The routing dash added in #59 surfaces failure/success rates, channel utilization and resolution time for htlcs that lnd processes.

One thing that's missing from this dash is htlc amounts, which also provide insight into node behaviour. Since the htlc stream is ephemeral, we may want to get this information from forwarding history, rather than our stream. Some things we could surface:
- Bar Graph of amounts (as is done for resolution time)
- Average htlc size (segmented by failure/success)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the routing dashboard added in #59 and how forwarding history exposes HTLC amounts, since the stream is ephemeral. Determine the intended amount visualizations, then verify that the dashboard shows an amount bar graph and average HTLC size segmented by failure and success.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, grafana, prometheus
Domain
data-visualization, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.