Consolidate provider-specific model IDs into a single display name for Dashboard telemetry

[Munsen]

The same underlying model is often exposed with different model IDs across providers. As a result, the Dashboard renders separate entries for what is effectively the same model.
For example, glm-5.1 is served under the following model IDs depending on the provider (Reference: https://models.dev/?search=glm-5.1):

Provider	Model ID
zai	glm-5.1
neuralwatt	zai-org/GLM-5.1-FP8
wafer.ai	GLM-5.1

When using these providers/models, the Dashboard outputs three separate data series for what is the same GLM model.

[mcowger]

I'm not sure I fully understand - but I believe this is intended behavior. Can you show me exactly what you mean?

[Munsen]

If you look at Live Metrics' Model Pulse and Provider & Model Stats, it is GLM-5.1, but the Provider's ModelId is different, so it is printed in two different models.

I'd like to combine these two.

If you used sonnet-3.5 in the open router and sonnet-3.5 in the anthropic, the model will not be shown in two because the modelId is the same.

[mcowger]

Got it. This is intentional behavior, as these are, in fact distinct models (in so far as they may be based on the same weights, but almost certainly have distinct inference settings and possibly quantizations).

[Munsen]

Hm... OK'
I'll tell you one more thing because I don't know if my example was enough.

Cloudflare AI Gateway serves Opus 4.5 as anthropic/claude-opus-4.5.
Azure serves Claude Opus 4.5 as claude-opus-4.5.

I don't expect it to be much different from Opus 4.5 serving Azure and Opus 4.5 serving Cloudflare AI Gateway.

That's why I wish the user could decide rather than be dependent on the provider's model id.

[mcowger]

The intent here is that the primary focus on usage etc is on the model alias, rather than the provider/target.

I would be open to changing model pulse to focus on aliases rather than targets.

Thoughts?

[Munsen]

I think the provider/model_id structure suits Live Metrics better as it is now.
If it's a new tab on Dashboard, maybe it's okay.

Thank you for your interest.