networkservicemesh / networkservicemesh/api
MonitorScopeSelector with optional NetworkService?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 22
- Avg merge
- 27m
- Merged PRs (30d)
- 3
Description
I'd be interested in NSM connections around the cluster that belong to a particular Network Service. The concept would be similar to cmd-dashboard-backend.
However, MonitorScopeSelector only allows PathSegment based filtering/subscription.
The processes doing the monitoring would have NO knowledge on the path segments involved (might come and go over time). Using an empty selector does work, but the reason why I'd be interested in Network Service based filtering is mostly due to performance considerations.
I've attached a rudimentary patch with the proposed changes.
api.txt
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 reading MonitorScopeSelector and the cmd-dashboard-backend concept described in the issue, then inspect the attached api.txt patch. Determine how an optional Network Service filter should coexist with PathSegment filtering and validate the API behavior against the stated monitoring and performance use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100