Add HTTP server and client active network connection gauge metrics #47554
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.
Add new HTTP Server
http_server_active_connections
and Clienthttp_client_active_connections
gauge metrics.The client metric will be available (just like many other such client metrics) only when the client is registered with metrics name programmatically as below:
where ExternalService is a Rest Client interface.
Another approach: I couldn't find a way to register the metrics name through annotations, so using
@RestClient
annotation will not register this metric along with some other metrics which fall into the same category unless ContextResolver for HttpClientOptions is registered as given here .