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
In the new Helidon metrics API, each meter can have a different scope (formerly called "registry type" in 3.x) or no scope. Currently, if the developer creates a meter without setting the scope explicitly or without setting the default scope in the MetricsConfig then the meter has no scope.
This is different from 3.x (in which the default scope was always application.)
For ease of migration, the new metrics API in SE should use application as the default scope (unless the developer changes it using MetricsConfig).
The text was updated successfully, but these errors were encountered:
Environment Details
Problem Description
In the new Helidon metrics API, each meter can have a different scope (formerly called "registry type" in 3.x) or no scope. Currently, if the developer creates a meter without setting the scope explicitly or without setting the default scope in the
MetricsConfig
then the meter has no scope.This is different from 3.x (in which the default scope was always
application
.)For ease of migration, the new metrics API in SE should use
application
as the default scope (unless the developer changes it usingMetricsConfig
).The text was updated successfully, but these errors were encountered: