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
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