You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the MicrometerObservationCapability (as autoconfigured by spring-cloud-openfeign) no information about the client is attached to the http.client.requests or http.client.requests.active meters.
This can be confusing for applications that have more than one feign client, especially when multiple clients have the same path template resulting in the metrics being merged.
For monitoring it would also useful to be able to filter metrics by client (different downstreams have different latency expected etc).
The text was updated successfully, but these errors were encountered:
When using the
MicrometerObservationCapability
(as autoconfigured by spring-cloud-openfeign) no information about the client is attached to thehttp.client.requests
orhttp.client.requests.active
meters.This can be confusing for applications that have more than one feign client, especially when multiple clients have the same path template resulting in the metrics being merged.
For monitoring it would also useful to be able to filter metrics by client (different downstreams have different latency expected etc).
The text was updated successfully, but these errors were encountered: