The current JMX export for metrics is using the default DropWizard metrics API domain (which is 'metrics').
When connecting to a Jenkins instance using JMX, it is not obvious at all that the domain 'metrics' is in fact hosting Jenkins metrics.
JMX best practices
The domain part of an Object Name should start with a Java package name. This prevents collisions between MBeans coming from different subsystems. There might be additional text after the package name. Examples:
Therefore, I propose to use io.jenkins as domain to expose metrics via JMX.
|Field||Original Value||New Value|
|Assignee||Vincent Latombe [ vlatombe ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||In Review [ 10005 ]|
|Remote Link||This issue links to "PR #47 (Web Link)" [ 23102 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Review [ 10005 ]||Resolved [ 5 ]|