Hi Peter, Have you compared the DAT topologies in 1.15 / 1.14?
I think it's expected that "Records Received", "Bytes Sent" and "Records Sent" are 0. These metrics trace the internal data exchanges between Flink tasks. External data changes, i.e., source reading / sink writing data from / to external systems, are not counted. In your case, there's only 1 vertex in the DAG, thus no internal data exchanges. Thank you~ Xintong Song On Wed, Apr 6, 2022 at 11:21 PM Peter Schrott <pe...@bluerootlabs.io> wrote: > Hi there, > > I just successfully upgraded our Flink cluster to 1.15.0 rc0 - also the > corresponding job is running on this version. Looks great so far! > > In the Web UI I noticed some metrics are missing, especially "Records > Received", "Bytes Sent" and "Records Sent". Those were shown in v 1.14.4. > See attached screenshot. > > Other than that I noticed, when using > org.apache.flink.metrics.prometheus.PrometheusReporter , the taskmanager > on which the job is running does not report the metrics on the configured > port. Rather it returns: > > ➜ ~ curl http://flink-taskmanager-xxxxxx:xxxx/ > curl: (52) Empty reply from server > > The other taskmanager reports metrics. > > The exporter is configured as followed: > > # Prometheus metrics > metrics.reporters: prom > metrics.reporter.prom.class: > org.apache.flink.metrics.prometheus.PrometheusReporter > metrics.reporter.prom.port: xxxxxx > > Is this a known issue with flink 1.15 rc0? > > Best, Peter > > [image: missingmetricsinui.png] >
