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
Currently we do not have metrics in fault tolerance components, and we did not introduce them to concurrency limits (#8897).
We should find a good way to be able to expose information from these components that can be seen in metrics.
We should honor the name of the component, to allow differentiation between instances (i.e. we can have a fixed metric for a client and a server, and these should not be seen in metrics as the same instance) - this can be achieved through name, which can be specified by user in configuration, or when explicitly setting an instance.
The text was updated successfully, but these errors were encountered:
Hi team,
Could you clarify what specific types of metrics will be emitted by this enhancement? Additionally, in which version of Helidon will these new metrics features be available for users?
Thanks,
David
Currently we do not have metrics in fault tolerance components, and we did not introduce them to concurrency limits (#8897).
We should find a good way to be able to expose information from these components that can be seen in metrics.
We should honor the name of the component, to allow differentiation between instances (i.e. we can have a fixed metric for a client and a server, and these should not be seen in metrics as the same instance) - this can be achieved through
name
, which can be specified by user in configuration, or when explicitly setting an instance.The text was updated successfully, but these errors were encountered: