flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chesnay Schepler <ches...@apache.org>
Subject Re: Task and Operator Monitoring via JMX / naming
Date Sat, 15 Oct 2016 09:52:47 GMT
Hello Philipp,

the relevant names are stored in the OperatorMetricGroup/TaskMetricGroup 
classes in flink-runtime.

The name for a task is extracted directly from the 
TaskDeploymentDescriptor in TaskManagerJobMetricGroup#addTask().
The name for a streaming operator that the metric system uses is set in 
AbstractStreamOperator#setup() and is derived
from the task name.


On 15.10.2016 10:08, Philipp Bussche wrote:
> Thanks Chesnay, this is on Flink 1.1.3
> Please also note that e.g. the first item in the list which has the custom
> metric attached to it starts with a leading "(". It might be that the
> parsing of the names is not working quite as expected.
> I was trying to find out where these names come from but wasn't able to
> identify it in the source. If you know and want to give me a hint I can also
> do some more debugging !
> Thanks
> Philipp
> --
> View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Task-and-Operator-Monitoring-via-JMX-naming-tp9560p9564.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.

View raw message