[GitHub] [beam] Sanil15 opened a new issue, #26456: Default transform metrics like throughput, latency & watermark progress for Beam Samza Runner

["Sanil15 (via GitHub)" <gi...@apache.org>]

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

   ### What needs to happen?
   
   **Summary**
   
   - Added Support for generating throughput, watermark progress & latency metric emission
   - A MetricOp is attached to each input & output
   - Throughput Metrics are emitted for input and output throughput
   - Watermark Progress Metrics are emitting at the during-process watermark of output
   - Latency Metrics are emitted by collecting avg arrival time at input & output per watermark for each transform using formula Latency = Avg
   - Arrival Time of Elements at Output - Avg Arrival Time of Elements at Input
   - For GroupByKey translator based operators we aggregate avg arrivial time per window id and then only emit the latency using bove formula for elements under the same window 
   
   
   
   ### Issue Priority
   
   Priority: 3 (nice-to-have improvement)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [ ] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [X] 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: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org