I instrument model usage at one chokepoint, with optional telemetry guarded so it can never block the primary request. That gives multi-model systems one safe measurement layer, while monitoring fails quietly.
where should model usage be instrumented in a multi-model system?
The useful place is one shared chokepoint. Every model request passes through the same measurement layer, so usage can be observed consistently across a multi-model system.
That keeps instrumentation focused on one boundary instead of scattering monitoring logic across individual model paths.
what happens when telemetry has a problem?
Telemetry stays optional and guarded. The primary request continues even when monitoring has an issue.
The monitoring layer should fail quietly, keeping measurement from becoming a dependency of the work it observes.
why does one safe measurement layer matter?
A single chokepoint creates one place to instrument model usage. It gives a multi-model system a shared view of activity without requiring every model path to carry its own measurement approach.
The design constraint is simple: observe the request, protect the request, and let monitoring disappear when it cannot do its job.
where is the best place to add model usage telemetry?
Add it at a shared chokepoint through which model requests pass. This gives multi-model systems one consistent measurement layer.
can telemetry block the primary model request?
It should never block the primary request. Guard optional telemetry so monitoring failures fail quietly.
how should monitoring behave when it breaks?
Monitoring should fail quietly while the primary request continues. Measurement remains useful without becoming part of the request's success condition.