Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2418
I think that works to expose the names. I was wondering, though, if we can
have a more JMX-natural integration.
The JMX `ObjectName` has the constructor `ObjectName(String domain,
Hashtable<String,String> table)`. Rather than having
`key1=taskmanager,key2=<hostname>,key3=<jobname>`, we could go for
`domain=taskmanager.task.operator.io.numRecords` (no variable parsing) and
`table={taskmanager=<tid>, hostname=<hostname>, jobid=<jid>, ...`. If I got the
thoughts of some of the users right, that would be the preferred way for them.
That probably contradicts the "configurable name" design we have for the
other reporters, because the table and the formatted scope/name override each
other (I think, not sure, not a JMX expert here).
In the end, both approaches are probably valid and which one is more usable
depends on the metric infrastructure of the users. So, if we cannot get both
into the same reporter, should we simply have two JMX reporters? A "tag-based"
(like discussed above) and a "name/scope-based" (like we have so far)?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
