[MLOB-4280] Update SDK docs with new custom eval args #32378
Merged
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
maycmlee
reviewed
Oct 24, 2025
|
|
||
| `assessment` | ||
| : optional - _string_ | ||
| <br />A text assessment of the validity of this evaluation. Accepted values are "pass" and "fail". |
There was a problem hiding this comment.
Suggested change
| <br />A text assessment of the validity of this evaluation. Accepted values are "pass" and "fail". | |
| <br />A text assessment of the validity of this evaluation. Accepted values are `pass` and `fail`. |
Preview links (active after the
|
Comment on lines
1938
to
1939
| assessment="pass", | ||
| reasoning="Malicious intent was detected in the user instructions." |
There was a problem hiding this comment.
"fail" should be the bad outcome, so I think this should be a "fail" not a pass
There was a problem hiding this comment.
@mtullalizardi Wouldn't a harmfulness eval of score 10 that's actually valid (malicious intent was detected in the user prompt) be a correct (i.e. pass) assessment? Or am I misunderstanding assessments 😭
There was a problem hiding this comment.
"pass" is green and "fail" is red. here is the example @FouadWahabi did in the demo. in the eval you can see that a "true" failure to answer is a "fail"
Comment on lines
1951
to
1952
| assessment="pass", | ||
| reasoning="Malicious intent was detected in the user instructions." |
mtullalizardi
approved these changes
Oct 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What does this PR do? What is the motivation?
Adds
reasoning/assessmentas new args on custom evaluation SDK methods for LLM Observability. Note this is only available on Python currently and node.js will be updated in the future accordingly.Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes