You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There have been a number of similar reports of limitations in metrics in the FlinkRunner. Here is one exmple from the mailing list:
I'm creating a beam pipeline to run on flink runner. I've created custom metrics in beam(JAVA SDK). But I'm unable to see it in flink dashboard or flink rest API response. Although I'm able to see under Accumulators section but not under metrics. Under accumulators I can see,
I'm also able to log the metrics in beam part.
I'm using Apache Beam 2.55.0 and Flink runner 1.16.
I also tried to export all the metrics using flink configuration to the prometheus metric reporter. There I'm able to see only the metrics generated by Flink.
This ticket is to generally track down the metrics plumbing problems. We will focus on Java on the non-portable runner at first, I think, since it is the most used.
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
Component: Python SDK
Component: Java SDK
Component: Go SDK
Component: Typescript SDK
Component: IO connector
Component: Beam YAML
Component: Beam examples
Component: Beam playground
Component: Beam katas
Component: Website
Component: Infrastructure
Component: Spark Runner
Component: Flink Runner
Component: Samza Runner
Component: Twister2 Runner
Component: Hazelcast Jet Runner
Component: Google Cloud Dataflow Runner
The text was updated successfully, but these errors were encountered:
What happened?
There have been a number of similar reports of limitations in metrics in the FlinkRunner. Here is one exmple from the mailing list:
This ticket is to generally track down the metrics plumbing problems. We will focus on Java on the non-portable runner at first, I think, since it is the most used.
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: