metrics: support pyroscope for continous profile

[bufferflies]

What problem does this PR solve?

Issue Number: Close #8957

What is changed and how does it work?

Check List

Tests

Code changes

Side effects

• Possible performance regression

Related changes

Release note

None.

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 21 lines in your changes missing coverage. Please review.

Project coverage is 76.19%. Comparing base (2bbeb9c) to head (275597d).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8958      +/-   ##
==========================================
- Coverage   76.25%   76.19%   -0.06%     
==========================================
  Files         468      468              
  Lines       71695    71716      +21     
==========================================
- Hits        54673    54646      -27     
- Misses      13610    13651      +41     
- Partials     3412     3419       +7     

Flag	Coverage Δ
unittests	76.19% <0.00%> (-0.06%)	⬇️

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

[bufferflies]

/merge

[ti-chi-bot]

@bufferflies: We have migrated to builtin LGTM and approve plugins for reviewing.

👉 Please use /approve when you want approve this pull request.

The changes announcement: Proposal: Strengthen configuration change approval.

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.

[bufferflies]

@okJiang ptal again

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nolouch, okJiang

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [nolouch]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-01-15 08:15:11.117250546 +0000 UTC m=+106382.572296695: ☑️ agreed by nolouch.
• 2025-01-17 07:58:13.23168731 +0000 UTC m=+278164.686733460: ☑️ agreed by okJiang.

[bufferflies]

/retest

[bufferflies]

/merge

[ti-chi-bot]

@bufferflies: We have migrated to builtin LGTM and approve plugins for reviewing.

👉 Please use /approve when you want approve this pull request.

The changes announcement: Proposal: Strengthen configuration change approval.

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.

[bufferflies]

/test pull-integration-realcluster-test

[bufferflies]

/retest

[bufferflies]

/test pull-integration-realcluster-test

[bufferflies]

/test pull-integration-realcluster-test

[bufferflies]

/test pull-integration-realcluster-test

[ti-chi-bot]

@bufferflies: 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.

[ti-chi-bot]

@bufferflies: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-integration-realcluster-test	275597d	link	true	/test pull-integration-realcluster-test

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.