You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/03 23:52:58 UTC

[GitHub] [beam] kennknowles opened a new issue, #19397: Encapsulate supplier, monitor and metric naming logic in some common TestMetric type

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

   After an offline discussion together with @mwalenia we decided to create concrete classes for each metric type (Item_count, byte_count, time). Each class like this will contain: 
   - metric name
   - supplier for the metric 
   - monitor for the metric
   
   It turns out that all this (along with the monitor/supplier can be encapsulated and then attached to the pipeline/metrics reading where needed. This will also encapsulate the naming logic (so that there are no typos again).
   
   Imported from Jira [BEAM-7245](https://issues.apache.org/jira/browse/BEAM-7245). Original Jira may contain additional context.
   Reported by: ŁukaszG.


-- 
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