Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.x SE meters should have default scope of application instead of no scope #7658

Closed
tjquinno opened this issue Sep 25, 2023 · 0 comments · Fixed by #7666
Closed

4.x SE meters should have default scope of application instead of no scope #7658

tjquinno opened this issue Sep 25, 2023 · 0 comments · Fixed by #7666
Assignees
Labels
4.x Version 4.x metrics
Milestone

Comments

@tjquinno
Copy link
Member

Environment Details

  • Helidon Version: 4.x
  • Helidon SE or Helidon MP SE
  • JDK version:
  • OS:
  • Docker version (if applicable):

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 using MetricsConfig).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.x Version 4.x metrics
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants