The current naming convention for the MBean object is based on the topic-prefix/dbservername, but it would be more logical to include the connector name in the MBean object name instead of the dbservername. Additionally, the current MBean naming system is rigid and does not allow users to add additional tags to the metrics.

To address these issues and introduce more flexibility, this proposal is to implement custom tags for the metrics. This change would involve introducing a new configuration that accepts key-value pairs to customize the MBean object name. Each key would represent a tag for the MBean object name, and the corresponding value would be the value of that tag.

With custom tags users will have the flexibility to organize and categorize metrics in a way that aligns with their operational needs. These tags can provide additional contextual information about the metrics. For example, users can include the tags that represent relevant dimensions, such as application instance, environment, region, version, or any other relevant metadata. This granular information can help in distinguishing metrics from different sources or environments. This improved flexibility empowers users to tailor the MBean object names and associated tags to their unique monitoring and operational practices.