metrics: fix the duplicate avg metrics

[nolouch]

What problem does this PR solve?

Issue Number: ref #7897

What is changed and how does it work?

metrics: fix the duplicate avg metrics

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  before
  

after

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• HuSharp
• JmPotato

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.27%. Comparing base (0f3e1f9) to head (447dd42).

❗ Current head 447dd42 differs from pull request most recent head 13ad370

Please upload reports for the commit 13ad370 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8210      +/-   ##
==========================================
- Coverage   77.29%   77.27%   -0.03%     
==========================================
  Files         471      471              
  Lines       61436    61436              
==========================================
- Hits        47490    47476      -14     
- Misses      10369    10398      +29     
+ Partials     3577     3562      -15     

Flag	Coverage Δ
unittests	77.27% <ø> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

[JmPotato]

/merge

[ti-chi-bot]

@JmPotato: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 447dd42

[ti-chi-bot]

@nolouch: Your PR was out of date, I have automatically updated it for you.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.