DAOS-17644 gurt:Add server object I/O latency histogram
Add server I/O latency histogram, and add %50 90% 99% latency to metrics.
Steps for the author:
- [ ] Commit message follows the guidelines.
- [ ] Appropriate Features or Test-tag pragmas were used.
- [ ] Appropriate Functional Test Stages were run.
- [ ] At least two positive code reviews including at least one code owner from each category referenced in the PR.
- [ ] Testing is complete. If necessary, forced-landing label added and a reason added in a comment.
After all prior steps are complete:
- [ ] Gatekeeper requested (daos-gatekeeper added as a reviewer).
Ticket title is 'Add server object I/O latency histogram' Status is 'Open' Errors are component not formatted correctly https://daosio.atlassian.net/browse/DAOS-17644
Test stage Build on EL 8.8 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-16477/1/execution/node/334/log
Test stage Build on Leap 15.5 with Intel-C and TARGET_PREFIX completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-16477/1/execution/node/339/log
Test stage Build RPM on EL 9 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-16477/1/execution/node/309/log
Test stage Build RPM on EL 8 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-16477/1/execution/node/343/log
Test stage Build RPM on Leap 15.5 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-16477/1/execution/node/310/log
@wangdi1: Shouldn't this go to master first? There are some changes to the telemetry library that are in master and google/2.6, but not release/2.6.
@wangdi1: Shouldn't this go to master first? There are some changes to the telemetry library that are in master and google/2.6, but not release/2.6.
Oops, I see that this is the second of two PRs. In any case, I think release/2.6 is only for bugfixes at this point. It would probably be cleaner to cherry-pick from master to google/2.6 after the master PR has been reviewed and landed.