Done,it's on the website now. Ryan and I will move forward with the plan in this plan. If there are any major objections to this plan, please let us know by weds. Suggestions will be welcome later as well, as we are happy to iterate on this. But we will be proceeding with some of Ryan's PRs based on this design.
On Thu, Jan 31, 2019 at 12:54 PM Ismaël Mejía <ieme...@gmail.com> wrote: > Please don't forget to add this document to the design documents webpage. > > On Thu, Jan 31, 2019 at 8:46 PM Alex Amato <ajam...@google.com> wrote: > > > > Hello Beam, > > > > Robert Ryan and I have been designing a metric extraction API for Beam. > Please take a look at this design, I would love to get more feedback on > this to improve the design. > > > > https://s.apache.org/get-metrics-api > > > > The primary goal of this proposal is to offer a simple way to obtain all > the metrics for a job. The following issues are addressed: > > > > The current design requires implementing metric querying for every > runner+language combination. > > > > Duplication of MetricResult related classes in each language. > > > > The existing MetricResult format only allows querying metrics defined by > a namespace, name and step, and does not allow generalized labelling as > used by MonitoringInfos. > > > > Enhance Beam’s ability to integration test new metrics > > > > > > Thank for taking a look, > > Alex >
