Introduce DefaultXdsLoadBalancerLifecycleObserver
#6490
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation:
When using xDS based clients, users will often want to know how the xDS resources translate to the load balancer which routes requests upstream.
This changeset attempts introduce a
DefaultXdsLoadBalancerLifecycleObserverwhich collects metrics of each load balancer for each cluster.This observer has the same lifecycle as a
ClusterResourceNode, and will deregister each metric upon close.Note that thanks to
XdsClusterManager, each cluster has a unique name.Modifications:
DefaultXdsLoadBalancerLifecycleObserveris introduced which records metrics for aXdsLoadBalancerMeterRegistry,MeterIdPrefixcan now be specified inXdsBootstrapBuilderMeterRegistry,MeterIdPrefixis also added toSubscriptionContextso that they can be accessed when dynamically querying xDS resourcesEventExecutoris used for the default event loop.Result:
DefaultXdsLoadBalancerLifecycleObservernow records metrics forXdsLoadBalancers by default