-
Notifications
You must be signed in to change notification settings - Fork 864
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
Updated Camel rules adding route.started rooute.added and thread pool… #12763
base: main
Are you sure you want to change the base?
Conversation
…s' pool.core_size
da3f2f0
to
9ce2d56
Compare
StartedRoutes: | ||
metric: route.started | ||
type: updowncounter | ||
unit: "{routes}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The semantic conventions for metric units recommend using singular form, so {route} rather than {routes}.
@@ -246,6 +260,11 @@ rules: | |||
type: updowncounter | |||
unit: "{threads}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be {thread}, according to the semantic conventions.
- bean: org.apache.camel:context=*,type=context,name=* | ||
prefix: camel.context. | ||
metricAttribute: | ||
context: param(context) | ||
camelVersion: beanattr(CamelVersion) | ||
packageScanClassResolver: beanattr(PackageScanClassResolver) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The semantic conventions for metric attributes suggest using underscores to separate individual words, so these apparently should rather be camel_version
and package_scan_class_resolver
. But, given that you merely copy the MBean attributes here, I'm not sure what is more user-friendly.
…s' pool.core_size