Reconsider auto-configuration of HierarchicalNameMapper #12676
Description
See #12557 (comment)
HierarchicalNameMapper is not a component that can be shared amongst multiple monitoring systems. Right now the auto-configuration for Ganglia, Graphite, JMX and Statsd all create an instance if none exists in the context.
Rather that adapting to the presence of such a bean in the context, we should probably go with whatever makes sense and offer another way to customize the mapper. The simplest would be to require the user to override the registry.
ping @jkschneider