Re: Task and Operator Metrics in Flink 1.3

2017-06-13 Thread Dail, Christopher
opher" Date: Tuesday, June 13, 2017 at 1:58 PM To: Chesnay Schepler , "user@flink.apache.org" Subject: Re: Task and Operator Metrics in Flink 1.3 I think I found the root cause of this problem. It has to do with how DC/OS metrics handling works. DC/OS passes special environm

Re: Task and Operator Metrics in Flink 1.3

2017-06-13 Thread Dail, Christopher
e with DC/OS metrics. Thanks Chris From: Chesnay Schepler <mailto:ches...@apache.org> Date: Tuesday, June 13, 2017 at 5:26 AM To: "user@flink.apache.org"<mailto:user@flink.apache.org> <mailto:user@flink.apache.org> Subject: Re: Task and Operator Metrics in Flink 1.3 The s

Re: Task and Operator Metrics in Flink 1.3

2017-06-13 Thread Chesnay Schepler
ate: *Tuesday, June 13, 2017 at 5:26 AM *To: *"user@flink.apache.org" *Subject: *Re: Task and Operator Metrics in Flink 1.3 The scopes look OK to me. Let's try to narrow down the problem areas a bit: 1. Did this work with the same setup before 1.3? 2. Are all task/operator metr

Re: Task and Operator Metrics in Flink 1.3

2017-06-13 Thread Dail, Christopher
ay, June 13, 2017 at 5:26 AM To: "user@flink.apache.org" Subject: Re: Task and Operator Metrics in Flink 1.3 The scopes look OK to me. Let's try to narrow down the problem areas a bit: 1. Did this work with the same setup before 1.3? 2. Are all task/operator metrics available

Re: Task and Operator Metrics in Flink 1.3

2017-06-13 Thread Chesnay Schepler
The scopes look OK to me. Let's try to narrow down the problem areas a bit: 1. Did this work with the same setup before 1.3? 2. Are all task/operator metrics available in the metrics tab of the dashboard? 3. Are there any warnings in the TaskManager logs from the MetricRegistry or StatsDRe

Task and Operator Metrics in Flink 1.3

2017-06-12 Thread Dail, Christopher
I’m using the Flink 1.3.0 release and am not seeing all of the metrics that I would expect to see. I have flink configured to write out metrics via statsd and I am consuming this with telegraf. Initially I thought this was an issue with telegraf parsing the data generated. I dumped all of the me