Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Story]: Kserve support for performance metrics #2099

Closed
alexcreasy opened this issue Nov 8, 2023 · 1 comment
Closed

[Story]: Kserve support for performance metrics #2099

alexcreasy opened this issue Nov 8, 2023 · 1 comment
Labels
feature/model-serving Model Serving Feature kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. migrated priority/high Important issue that needs to be resolved asap. Releases should not have too many of these.

Comments

@alexcreasy
Copy link
Contributor

alexcreasy commented Nov 8, 2023 •
edited
Loading

Goal

Ensure our performance metrics features for both the model server and also models themselves work with Kserve in addition to model mesh

Dependency issue

Itemized goals

  • Add Kserve support for model server metrics
  • Add Kserve support for model inference metrics

Aspects continued elsewhere

No response

Mocks

No mocks
@alexcreasy alexcreasy added priority/high Important issue that needs to be resolved asap. Releases should not have too many of these. feature/model-serving Model Serving Feature kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. labels Nov 8, 2023
@alexcreasy alexcreasy mentioned this issue Nov 8, 2023
Closed
@dgutride
Copy link
Contributor

dgutride commented Dec 1, 2023

Migrated to https://issues.redhat.com/browse/RHOAIENG-246 - moving to closed

@dgutride dgutride closed this as completed Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature/model-serving Model Serving Feature kind/story A user story for larger work. Should always be referenced by a "tracker" labelled issue. migrated priority/high Important issue that needs to be resolved asap. Releases should not have too many of these.
Projects
No open projects
ODH Dashboard Planning
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexcreasy @dgutride