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

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

                Author: ASF GitHub Bot
            Created on: 24/Apr/20 03:33
            Start Date: 24/Apr/20 03:33
    Worklog Time Spent: 10m 
      Work Description: lukecwik commented on pull request #11514:
URL: https://github.com/apache/beam/pull/11514#issuecomment-618782738


   > I suppose this would be to finish the transition from reporting counters 
on PTransform outputs to recording them on the various PCollections.
   > 
   > LGTM if you can change to use a mapping of tags to pcoll ids rather than 
relying on ordering being the same.
   
   I'll try it out but I worry that the consumers/receivers are either using 
indices or the post string converted tag names since python does some post 
processing converting the string tags to non string tags.


----------------------------------------------------------------
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: 426845)
    Time Spent: 1h 20m  (was: 1h 10m)

> Python SDK sending unexpected MonitoringInfo
> --------------------------------------------
>
>                 Key: BEAM-9488
>                 URL: https://issues.apache.org/jira/browse/BEAM-9488
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>            Reporter: Ruoyun Huang
>            Assignee: Luke Cwik
>            Priority: Minor
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> element_count metrics is supposed to be tied with pcollection ids, but by 
> inspecting what is sent over by python sdk, we see there are monitoringInfo 
> sent wit ptransforms in it. 
> [Double checked the job graph, these seem to be redundant. i.e. the 
> corresponding pcollection does have its own MonitoringInfo reported.]
> Likely a bug. 
> Proof: 
> urn: "beam:metric:element_count:v1"
> type: "beam:metrics:sum_int_64"
> metric {
>   counter_data {
>     int64_value: 1
>   }
> }
> labels {
>   key: "PTRANSFORM"
>   value: "start/MaybeReshuffle/Reshuffle/RemoveRandomKeys-ptransform-85"
> }
> labels {
>   key: "TAG"
>   value: "None"
> }
> timestamp {
>   seconds: 1583949073
>   nanos: 842402935
> }



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

Reply via email to