This is completely unintended behavior; you should never have to adjust
your topology so the metric system get's the names right.
I'll take a deep look into this tomorrow ;)
Regards,
Chesnay
On 20.10.2016 08:50, Philipp Bussche wrote:
Some further observations: I had a Job which was taking events of a Kafka
topic and sending it to two sinks whereas for one of them a Map operation
would happen first. When creating one event stream and sending it to the two
sinks the JMX representation was not showing both sinks and the naming of
the Map operation was also not right. But when creating two event streams in
the job (basically two Kafka consumers doing the exact same) and then
sending each to one sink the naming changed and seem to look like what I
would expect.
A question remains though if it is best practise anyways to do one thing
with a Job only (like one map operation and one distribution to a sink) and
hence having multiple streams is the way to go or if this is still
unexpected behaviour what I see in my environment and should be fixed ?
Thanks
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Task-and-Operator-Monitoring-via-JMX-naming-tp9560p9642.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at
Nabble.com.
