Add silentdrop-llm to Observability (runtime guard for silent LLM-response failures)#551
Open
sravan27 wants to merge 1 commit into
Open
Add silentdrop-llm to Observability (runtime guard for silent LLM-response failures)#551sravan27 wants to merge 1 commit into
sravan27 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds silentdrop-llm under Observability. It catches the silent failure modes of LLM/agent responses — missing required fields, enum drift (e.g. "in-progress" when the schema says "in_progress"), hallucinated IDs that reference nothing in the lookup context, and claim/list mismatches — none of which throw, all of which silently produce wrong downstream data.
Fits next to QWED, EvalView, Giskard, and Fiddler in that section — same lane (runtime validation of LLM outputs) with a different focus: zero-dep, drop-in between the model call and any side-effecting use of the response.
Happy to adjust the section / wording if you'd prefer a different placement.