I had an offline discussion with @zentol, he said:
"I hope to get this change in for 1.5; the core implementation is done but
some details must be ironed out first.".
Best.
2018-01-03 11:25 GMT+08:00 Marvin777 <
[hidden email]>:
> Hi, all:
>
> I have some question about LatencyGauge change to histogram metric.
> Whether such a scheme is feasible?
>
> I want to know the latest progress on the question of FLINK-7608.
>
> @zentol, you suggested that we should delay merging this PR by a week or
> 2, and now What should I do in my version 1.3.1.
>
> Sorry to disturb, Regards,
>
> thanks all.
>
> 2017-09-09 4:36 GMT+08:00 Hai Zhou (JIRA) <
[hidden email]>:
>
>> Hai Zhou created FLINK-7608:
>> -------------------------------
>>
>> Summary: LatencyGauge change to histogram metric
>> Key: FLINK-7608
>> URL:
https://issues.apache.org/jira/browse/FLINK-7608>> Project: Flink
>> Issue Type: Bug
>> Components: Metrics
>> Reporter: Hai Zhou
>> Assignee: Hai Zhou
>> Fix For: 1.4.0, 1.3.3
>>
>>
>> I used slf4jReporter[
https://issues.apache.org/jira/browse/FLINK-4831]
>> to export metrics the log file.
>> I found:
>>
>>
>> {noformat}
>> -- Gauges ------------------------------------------------------------
>> ---------
>> ......
>> zhouhai-mbp.taskmanager.f3fd3a269c8c3da4e8319c8f6a201a57.Flink Streaming
>> Job.Map.0.latency: value={LatencySourceDescriptor{vertexID=1,
>> subtaskIndex=-1}={p99=116.0, p50=59.5, min=11.0, max=116.0, p95=116.0,
>> mean=61.833333333333336}}
>> zhouhai-mbp.taskmanager.f3fd3a269c8c3da4e8319c8f6a201a57.Flink Streaming
>> Job.Sink- Unnamed.0.latency: value={LatencySourceDescriptor{vertexID=1,
>> subtaskIndex=0}={p99=195.0, p50=163.5, min=115.0, max=195.0, p95=195.0,
>> mean=161.0}}
>> ......
>> {noformat}
>>
>>
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.4.14#64029)
>>
>
>
Locked
