[Feature]: Distinguish LoRA Model Metrics from Base Model Metrics in Reporting

[Jeffwan]

🚀 The feature, motivation and pitch

When submitting requests to a LoRA model and subsequently checking the associated metrics, I've noticed that all metrics are aggregated under the base model's metrics. This means that requests made to the LoRA model are being counted as requests to the base model. Given that LoRA models logically represent a distinct model layer on top of the base, it is crucial for accurate monitoring and analysis that we separate these metrics.

part of #6275

curl http://localhost:8000/v1/completions \
    -H "Content-Type: application/json" \
    -d '{
        "model": "sql-lora",
        "prompt": "San Francisco is a",
        "max_tokens": 7,
        "temperature": 0
    }' 

Expected Behavior

Metrics for LoRA models should be distinctly reported, separate from the base model metrics, to accurately reflect their usage and performance.

Alternatives

No response

Additional context

No response

Before submitting a new issue...

• Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

[Jeffwan]

This has been improved in our env, I forgot to submit changes to upstream. I will work on a a fix shortly

[jeejeelee]

Thanks, Jeff

[github-actions]

This issue has been automatically marked as stale because it has not had any activity within 90 days. It will be automatically closed if no further activity occurs within 30 days. Leave a comment if you feel this issue should remain open. Thank you!

[github-actions]

This issue has been automatically closed due to inactivity. Please feel free to reopen if you feel it is still relevant. Thank you!