-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[V1][Metrics] Hook up IterationStats for Prometheus metrics #12478
[V1][Metrics] Hook up IterationStats for Prometheus metrics #12478
Conversation
Follow on from vllm-project#12416 Pass IterationStats to the stat logger, and log them in both the logging and prometheus loggers. For the logging stat logger, we need to calculate the throughput based on the number of tokens in the particular logging interval. In the prometheus logger, we just need to record the prompt and generation tokens in a counter. Note, v0 had a vllm:tokens_total counter registered that apparently was never logged to, so I've omitted it in v1. Signed-off-by: Mark McLoughlin <[email protected]>
👋 Hi! Thank you for contributing to the vLLM project. 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 do one of these:
🚀 |
LGTM |
…ject#12478) Signed-off-by: Mark McLoughlin <[email protected]>
…ject#12478) Signed-off-by: Mark McLoughlin <[email protected]> Signed-off-by: Isotr0py <[email protected]>
…ject#12478) Signed-off-by: Mark McLoughlin <[email protected]>
Follow on from #12416, part of #10582
Pass
IterationStats
to the stat logger, and log them in both the logging and prometheus loggers.For the logging stat logger, we need to calculate the throughput based on the number of tokens in the particular logging interval.
In the prometheus logger, we just need to record the prompt and generation tokens in a counter.
Note, v0 had a
vllm:tokens_total
counter registered that apparently was never logged to, so I've omitted it in v1.