Added rules for capturing Apache Camel metrics exposed by JMX MBeans

[luigidemasi]

No description provided.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: luigidemasi / name: Luigi De Masi (01aaed1)

[steverao]

There is a CI failure, you can solve it by referring to https://gradle.com/s/u5ny7filkybd2

[luigidemasi]

There is a CI failure, you can solve it by referring to https://gradle.com/s/u5ny7filkybd2

@steverao it should be fixed now

[laurit]

@PeterF778 do you have any guidance on how the metrics should be named. The existing ones aren't particularly consistent and use CamelCase, camelCase and dot.separated.

[PeterF778]

@PeterF778 do you have any guidance on how the metrics should be named. The existing ones aren't particularly consistent and use CamelCase, camelCase and dot.separated.

The metrics defined by semantic conventions clearly promote dot-separated names, both for the metric names and for the metric attribute names. I think we should follow this pattern as much as possible and practical. Just my 2 cents.

[trask]

The metrics defined by semantic conventions clearly promote dot-separated names, both for the metric names and for the metric attribute names. I think we should follow this pattern as much as possible and practical. Just my 2 cents.

also underscores for multi-word components of the name, e.g. jvm.memory.used_after_last_gc

(also see general naming guidelines at https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/attribute-naming.md)

[trask]

thanks! left a last few suggestions

[trask]

thanks @luigidemasi!