Richer prom metrics

[kfswain]

What would you like to be added: We would like richer, unaggregated inferencePool metrics to allow the user to perform their own aggregations

Why is this needed: the necessity is discussed here https://github.com/kubernetes-sigs/gateway-api-inference-extension/pull/304/files#r1947016924

[kfswain]

/assign @JeffLuoo

[k8s-ci-robot]

@kfswain: GitHub didn't allow me to assign the following users: JeffLuoo.

Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @JeffLuoo

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.

[kfswain]

@JeffLuoo if you dont mind saying hello here, we can get this assigned to ya

[JeffLuoo]

Can you provide some examples of what metrics we want to aggregate on inferencePool level? Do you have any proposal for it I can review? Thanks.

[kfswain]

This issue was created from a PR of yours, at your request, the comment should have all the context

[JeffLuoo]

I see, thanks. cc: @raywainman @smarterclayton

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[zhengkezhou1]

Hi @JeffLuoo do you mind if I pick up this ticket?