lightninglabs / lightninglabs/faraday
No outliers reported
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 130
- Forks
- 35
- Avg merge
- 7h 54m
- Merged PRs (30d)
- 5
Description
I run c-otto.de which has around 240 channels with various characteristics. I've been running faraday for a while now (more than a year?) and never ever saw any outlier, aside from the "uptime" metrics. This cannot be right, which is why I'm raising this issue. I wasn't able to attract any attention in Slack.
**Expected behavior**
`frcli outliers --revenue` or `frcli outliers --volume` sometimes show some outliers.
**Actual behavior**
No recommendations are shown.
**To reproduce**
* Start the node, start faraday, wait a bit (7 days)
* `frcli outliers --revenue --outlier_mult 1.5 --min_monitored 604800 | grep true -C 1000`
* `frcli outliers --volume --outlier_mult 1.5 --min_monitored 604800 | grep true -C 1000`
**System information**
Standalone, CLI access. I'm running v0.2.5-alpha from GitHub.
Linux 5.10.0-8-amd64, 4 vCPUs, 16 GByte RAM, SSD.
Debian Stable.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report with the `frcli outliers --revenue` and `frcli outliers --volume` commands after at least 7 days of monitoring. Compare behavior with the supplied `--outlier_mult 1.5` and `--min_monitored 604800` options; done means the commands produce appropriate outlier recommendations rather than none at all.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- analytics, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100