Glad you got it working, and thanks for letting us know!
David
On Thu, Sep 10, 2020 at 2:40 PM Pankaj Chand
wrote:
> Actually, I was wrong. It turns out I was setting the values the wrong way
> in conf/flink-conf.yaml.
> I set "metrics.latency.interval 100" instead of
Actually, I was wrong. It turns out I was setting the values the wrong way
in conf/flink-conf.yaml.
I set "metrics.latency.interval 100" instead of "metrics.latency.interval:
100". Sorry about that.
T
On Thu, Sep 10, 2020 at 7:05 AM Pankaj Chand
wrote:
> Thank you, David!
>
> After setting
Thank you, David!
After setting ExecutionConfig for latency tracking in the
SocketWindowWordCount Java source code and rebuilding and using that
application jar file, I am now getting the latency tracking metrics using
the REST endpoint. The below documentation [1] seems to imply that
merely
Pankaj,
I just checked, and the latency metrics for SocketWindowWordCount show up
just fine for me with Flink 1.11.1. For me, the latency metrics existed
even before I provided any data on the socket for the job to process. This
makes sense, as the latency tracking markers will propagate through
Hi David,
Thanks for replying! Sorry, I forgot to mention I am using Flink Version:
1.11.1, Commit ID: 7eb514a.
Is it possible that the default SocketWindowWordCount job is too simple to
generate Latency metrics? Or that the latency metrics disappear from the
output JSON when the data ingestion
Pankaj,
The Flink web UI doesn't do any visualizations of histogram metrics, so the
only way to access the latency metrics is either through the REST api or a
metrics reporter.
The REST endpoint you tried is the correct place to find these metrics in
all recent versions of Flink, but somewhere
Hello,
How do I visualize (or extract) the results for Latency Tracking for a
Flink local cluster? I set "metrics.latency.interval 100" in the
conf/flink-conf.yaml file, and started the cluster and
SocketWindowWordCount job. However, I could not find the latency
distributions anywhere in the web
