kennknowles opened a new issue, #32895:
URL: https://github.com/apache/beam/issues/32895

   ### 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:
   
   > 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, 
   > 
   > `{ "metrics": { "attempted": [{ "urn": "beam:metric:user:sum_int64:v1", 
"type": "beam:metrics:sum_int64:v1", "payload": "FA==", "labels": { 
"NAMESPACE": "Bingo", "NAME": "bingotest", "PTRANSFORM": 
"log/ParMultiDo(LogOutput)" } }] } }`
   >
   > I'm also able to log the metrics in beam part.
   > I'm using Apache Beam 2.55.0 and Flink runner 1.16.
   
   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
   - [X] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to