Telemetry: Improve system status at scale
- Dominant language
- C++
- Stars
- 16.7k
- Forks
- 1.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 126
Description
Current `fdbcli status` provides the status of the entire system. It does not scale well when a cluster scales (i.e., having more machines).
Sub-issues under this topic (umbrella issue):
- [ ] PR #1542: Enable exposing each field in `fdbcli status` individually;
- [ ] PR #2154: Push metrics to daemon service;
- [ ] PR https://github.com/apple/foundationdb/issues/2155: Make `status` cheaper (statuslite);
- [ ] PR #2159: Allows operators to know if an address (ip:port) has been successfully exclude.
- [ ] PR #2163: Identify where traffic is coming from.
Contributor guide
Research direction
Start with the `fdbcli status` command and review the linked sub-issues: PR #1542, PR #2154, issue #2155, PR #2159, and PR #2163. Determine which remaining status-at-scale work is in scope here; the umbrella issue is complete only when the relevant sub-issues and their operator-facing status improvements are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100