On Tue, Sep 21, 2021 at 3:45 PM Dave Marion <[email protected]> wrote: > > There is a WIP pull request against 2.1.0-SNAPSHOT for replacing the Hadoop > Metrics2 framework with Micrometer[1]. Micrometer suggests using a naming > pattern[2] for the metrics internally where words are all lowercase > separated by a period. Micrometer output formats then rewrite the metric > names to the destination specific format. It's possible that we may not be > able to produce metrics in the same exact way as the Hadoop Metrics2
Is it only the naming pattern that will cause incompatibility, or is it more than that? Like would a timer, guage, etc in micrometer produce different information/metrics than a timer,gauge,etc in hadoop metrics? I suspect these would differ and that would also impact compat. Will the way in which accumulo is configured to report metrics also change? I can't imagine it would be the same, but I have not looked at the PR. Can you provide an example of a naming incompat where it has to change? > framework. Metrics are not part of the public API, but we do want to try > and retain as much backwards compatibility as possible. In the event that > we cannot get that compatibility it has been suggested that we document how > things are different. As I have limited knowledge of how the metrics are Is there a reasonable path to achieving compatibility? If not, it seems like documenting what has changed is a good way to go. Could possibly explain it in detail in the 2.1.0 release notes and have a link to that in the user manual. > being used today, I'm looking for some feedback from the community as to > how painful it would be if metric names changed in a minor release. > > [1] https://micrometer.io/ > [2] https://micrometer.io/docs/concepts#_naming_meters
