numaflow
numaflow copied to clipboard
Latency metrics not visited or not documented in Reduce UDF
Describe the bug
As far as I check up on the Golang pkg/ directory with grep -ir and VScode, some latency metrics are documented in the Operator Manual but not visited in Reduce UDF. And other some ones are visited but not documented. Please see the following table for deatils.
| Metric name | Described in the Operator Manual | Visited in Reduce UDF |
|---|---|---|
| forwarder_read_processing_time | yes | no |
| forwarder_write_processing_time | yes | no |
| forwarder_ack_processing_time | yes | no |
| forwarder_udf_processing_time | yes | no |
| forwarder_concurrent_udf_processing_time | no | no |
| forwarder_forward_chunk_processing_time | yes | no |
| reduce_pnf_process_time | yes | no |
| reduce_pnf_forward_time | yes | no |
| reduce_pbq_write_time | no | yes |
Expected behavior
- reduce_pbq_write_time -- Documented.
- forwarder_udf_processing_time -- Visited in case of non-concurrent Reduce UDF.
- forwarder_concurrent_udf_processing_time -- Documented. Also visited in case of concurrent Reduce UDF.
- forwarder_forward_chunk_processing_time -- Documented as it is only visited in Map UDF.
- The others -- Visited.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We often sort issues this way to know what to prioritize.
For quick help and support, join our slack channel.