Uplink monitoring
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- grafana, python
- Domain
- networking, observability-sre
Research direction
The issue does not name files, tests, or an implementation entry point. Start by locating the repository’s existing monitoring and Grafana configuration, then determine how uplink checks should be collected and displayed. Done means monitoring covers ping, latency, and packet loss, with the expected failure or alert behavior documented.
Written by the indexing model from the issue text.
Description
Add monitoring for the uplink this should include but is not limited to:
- Ping
- Latency
- Packet loss
Please add your own suggestions in the comments of this issues
This should shorten the potential downtime if an automatic failover would fail (if we even can get that configured on our router)
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from 12urenloop/monitoring
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
12urenloop/monitoring#11 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
12urenloop/monitoring#9 ·
All issues in 12urenloop/monitoring
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100