Skip to content

[Metrics] Add --show-hidden-metrics-for-version CLI arg #13295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

markmc
Copy link
Member

@markmc markmc commented Feb 14, 2025

Part of #10582 and discussed in #12745

Add some infrastructure to help us deprecate and remove metrics in a less user-hostile way.

Our deprecation process will now be:

  1. Deprecate the metric in 0.N.0 - document the deprecation in
    release notes, user-facing docs, and the help text in /metrics
  2. Hide the metric in 0.N+1.0 - users can still re-enable the
    metrics using --show-hidden-metrics-for-version=0.N.0 as an
    escape hatch
  3. Remove the metric completely in 0.N+2.0

--show-hidden-metrics takes a version string argument so that users cannot fall into the habit of always enabling all deprecated metrics, which would defeat the purpose.

This approach is copied directly from kubernetes/kubernetes#85270

Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

@mergify mergify bot added documentation Improvements or additions to documentation v1 labels Feb 14, 2025
@markmc markmc force-pushed the metrics-v1-show-hidden-metrics-for-version branch from 52c20bf to b02294b Compare February 14, 2025 15:46
Add some infrastructure to help us deprecate and remove metrics
in a less user-hostile way.

Our deprecation process will now be:

1) Deprecate the metric in 0.N.0 - document the deprecation in
   release notes, user-facing docs, and the help text in `/metrics`
2) Hide the metric in 0.N+1.0 - users can still re-enable the
   metrics using `--show-hidden-metrics-for-version=0.N.0` as an
   escape hatch
3) Remove the metric completely in 0.N+2.0

`--show-hidden-metrics` takes a version string argument so that
users cannot fall into the habit of always enabling all deprecated
metrics, which would defeat the purpose.

This approach is copied directly from kubernetes/kubernetes#85270

Signed-off-by: Mark McLoughlin <[email protected]>
@markmc markmc force-pushed the metrics-v1-show-hidden-metrics-for-version branch from b02294b to b7ca51b Compare February 15, 2025 17:10
@robertgshaw2-redhat robertgshaw2-redhat added the ready ONLY add when PR is ready to merge/full CI is needed label Feb 20, 2025
if __version_tuple__[0:2] == (0, 0):
return True

# Note - this won't do the right thing when we release 1.0!
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we could asset that the version is not 1.0 so that we catch this when upgrading?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can be done as a follow up.

Copy link
Collaborator

@robertgshaw2-redhat robertgshaw2-redhat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very sensible

@robertgshaw2-redhat robertgshaw2-redhat enabled auto-merge (squash) February 20, 2025 22:31
@simon-mo simon-mo merged commit 2cb8c15 into vllm-project:main Feb 22, 2025
43 of 60 checks passed
lulmer pushed a commit to lulmer/vllm that referenced this pull request Apr 7, 2025
shreyankg pushed a commit to shreyankg/vllm that referenced this pull request May 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation ready ONLY add when PR is ready to merge/full CI is needed v1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants