[ 
https://issues.apache.org/jira/browse/BEAM-11092?focusedWorklogId=503927&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-503927
 ]

ASF GitHub Bot logged work on BEAM-11092:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Oct/20 23:08
            Start Date: 22/Oct/20 23:08
    Worklog Time Spent: 10m 
      Work Description: ajamato commented on a change in pull request #13163:
URL: https://github.com/apache/beam/pull/13163#discussion_r510506861



##########
File path: model/fn-execution/src/main/proto/beam_fn_api.proto
##########
@@ -306,18 +351,18 @@ message ProcessBundleProgressRequest {
   string instruction_id = 1;
 }
 
-// A request to provide full MonitoringInfo for a given id.
+// A request to provide full MonitoringInfo for a given bundle.
 //
 // An SDK can report metrics using an identifier that only contains the
 // associated payload. A runner who wants to receive the full metrics
 // information can request all the monitoring metadata via a
 // MonitoringInfosMetadataRequest providing a list of ids as necessary.
 //
-// The MonitoringInfo ids are scoped to the associated control connection. For
-// example, an SDK may reuse the ids across multiple bundles.
+// The SDK is allowed to reuse the identifiers across multiple bundles as long
+// as the MonitoringInfo could be reconstructed fully by overwriting its
+// payload field with the bytes specified here.
 message MonitoringInfosMetadataRequest {
-  // A list of ids for which MonitoringInfo are requested. All but the payload
-  // field will be populated.
+  // A list of ids for which the full MonitoringInfo is requested for.
   repeated string monitoring_info_id = 1;
 }
 

Review comment:
       I believe I have applied all of your suggestions now. I did some through 
this webpage and some locally.




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

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


Issue Time Tracking
-------------------

    Worklog Id:     (was: 503927)
    Time Spent: 1h 10m  (was: 1h)

> Add support for GCP IO metrica
> ------------------------------
>
>                 Key: BEAM-11092
>                 URL: https://issues.apache.org/jira/browse/BEAM-11092
>             Project: Beam
>          Issue Type: Test
>          Components: beam-model
>            Reporter: Alex Amato
>            Assignee: Alex Amato
>            Priority: P2
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> This involves, collecting new metrics from the IO libraries. And adding 
> "process wide" "harness metric" APIs. Metrics which are not bound to a bundle.
> [_https://s.apache.org/beam-gcp-debuggability_]
> In addition to adding a histogram style metrics.
> [https://s.apache.org/beam-histogram-metrics]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to