When models are defined in the config file they have the prometheus metric: litellm_proxy_total_requests_metric_total but if models are defined in gui and become "DB Model" in their status on the "models" page then they don't have this metric populated. They have other metrics that work but not this one.
Way to reproduce,
have 1 model in the config
have 1 model added via the gui
use both models
look at the /metrics page and you will only see "litellm_proxy_total_requests_metric_total" metrics for the config model
A metric that will work for both models is: litellm_request_total_latency_metric_sum
What happened?
When models are defined in the config file they have the prometheus metric: litellm_proxy_total_requests_metric_total but if models are defined in gui and become "DB Model" in their status on the "models" page then they don't have this metric populated. They have other metrics that work but not this one.
Way to reproduce,
have 1 model in the config have 1 model added via the gui use both models look at the /metrics page and you will only see "litellm_proxy_total_requests_metric_total" metrics for the config model
A metric that will work for both models is: litellm_request_total_latency_metric_sum
Relevant log output
Twitter / LinkedIn details
No response