hjtran opened a new issue, #36267: URL: https://github.com/apache/beam/issues/36267
### What would you like to happen? It looks like most of the components are in place for implementing histograms in the python sdk. There's the proto for the monitoring implemented here: https://github.com/apache/beam/pull/34017 And histogram util classes. I think maybe the only thing left is to just glue them together by implementing `HistogramCell.to_runner_api_monitoring_info`[link](https://github.com/apache/beam/blob/17c85154690573bb7cd4db1c2afae3b72037869b/sdks/python/apache_beam/internal/metrics/cells.py#L68) along with other proto encoding/decoding logic in [monitoring_infos.py](https://github.com/apache/beam/blob/17c85154690573bb7cd4db1c2afae3b72037869b/sdks/python/apache_beam/metrics/monitoring_infos.py#L399) ### Issue Priority Priority: 2 (default / most feature requests should be filed as P2) ### Issue Components - [x] 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 -- 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]
