Attaching the monitoring_infos received, if helpful.
I observed that the PCOLLECTION name format is the same in
non-portable mode, but the PTRANSFORM name has dashes instead.
```
monitoring_infos {
urn: "beam:metric:element_count:v1"
type: "beam:metrics:sum_int64:v1"
payload: "\000"
labels {
key: "PCOLLECTION"
value: "Kati-Step-2/ParMultiDo(Anonymous).output"
}
}
monitoring_infos {
urn: "beam:metric:user:sum_int64:v1"
type: "beam:metrics:sum_int64:v1"
payload: "\n"
labels {
key: "NAME"
value: "count101"
}
labels {
key: "NAMESPACE"
value: "org.apache.beam.runners.samza.portable.SamzaPortableTest"
}
labels {
key: "PTRANSFORM"
value: "Kati-Step-2-ParMultiDo-Anonymous-"
}
}
```
On Wed, Jan 11, 2023 at 2:38 PM Katie Liu <[email protected]> wrote:
> Hi beam-dev,
>
> I have a question regarding the PTransform name formatting.
> For the same user defined function, the naming is different using samza
> portable is "Kati-Step-2-ParMultiDo-Anonymous-", while in normal mode it
> is "Kati-Step-2/ParMultiDo(Anonymous)".
>
> Does this problem only exist in Samza? And are there pointers to where the
> PTransform name is generated?
>
> Thanks,
> Katie
>
