-
Notifications
You must be signed in to change notification settings - Fork 204
[metrics]: Allow EPP to register metrics from extension #1787
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
Conversation
The motivation is llm-d/llm-d-inference-scheduler#386 that we would like to have more metrics from llm-d inference scheduler plugin. The current metrics implementation is bundled in the runner of EPP, so this PR extends the runner to allow extention to register prometheus metrics collector. See llm-d/llm-d-inference-scheduler#405 for a draft PR of how metrics are going to be implemented in the plugin. I have tested locally that both EPP and inference scheduler metrics can be exported through the pod /metrics endpoint.
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/lgtm |
|
/lgtm Thanks Jeff! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JeffLuoo, kfswain, nirrozenbaum 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:
Approvers can indicate their approval by writing |
|
I want to make it to llm-d 0.4 release. @kfswain Hi Kellen, are you going to cut a branch for llm-d 0.4 or it will use 1.1.0? If 1.1.0 will be used, I would like this PR to be cherry-picked. Thanks! |
The motivation is
llm-d/llm-d-inference-scheduler#386 that we would like to have more metrics from llm-d inference scheduler plugin.
The current metrics implementation is bundled in the runner of EPP, so this PR extends the runner to allow extension to register prometheus metrics collector.
See llm-d/llm-d-inference-scheduler#405 for a draft PR of how metrics are going to be implemented in the plugin.
I have tested locally that both EPP and inference scheduler metrics can be exported through the pod /metrics endpoint.
What type of PR is this?
What this PR does / why we need it:
llm-d/llm-d-inference-scheduler#386
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: