Job level network metrics: should it be the average or aggression of all taskroles?
Open
Nobody has claimed this yet.
C-YH
ops-opt
raised by customer
service metrics/monitoring
system
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
Currently, we display the average of all taskroles bandwidth.
If we have two taskroles, with each 20M, the joblevel bandwidth would be 20M.
It's some kind of confusion.
For network bandwidth metric, joblevel metric may need to aggregate all taskroles.
Touch @xudifsd @YanjieGao @fanyangCS for discussion.
What would you like to be added:
Why is this needed:
Without this feature, how does the current module work：
Components that may involve changes:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.