Provider failures during chat can't be attributed to a provider or model from the logs #15603
drioatbu
started this conversation in
Feature Requests & Suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
When a provider call fails during a normal chat, the log entry is:
No provider, model, or error name. We hit this during a provider capacity incident: users were getting errors, the logs showed only that line, and we had to go to the vendor console to find out which provider and model were rejecting requests.
We patched our instances to log the failure with context. Same event, taken from our production logs:
Every field is known at the catch site. The latency alone told us the SDK had been retrying for 100 seconds before the user saw an error.
Summarization failures already log this via
describeProviderErrorin@librechat/agents(#12737), for example:with
provider,model,errorNameandstatusattached as metadata for JSON output.Could chat completion, title generation, and the OpenAI-compatible API failures use the same shape? Kept within the
getSafeErrorMetadatarules (no response bodies or headers). Format is your call; we used key=value in the message because the default console drops metadata, but the same fields as metadata would work withCONSOLE_JSON.Happy to open PRs if that helps.
All reactions