Add AI Guard example with content parts for Ruby#35837
Closed
y9v wants to merge 2 commits into
Closed
Conversation
Contributor
Preview links (active after the
|
maycmlee
approved these changes
Apr 8, 2026
maycmlee
left a comment
maycmlee
left a comment
Contributor
There was a problem hiding this comment.
LGTM! Feel free to merge when ready
Member
Author
|
Closing in favor of #35869 |
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
2 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?
This PR adds an example of evaluating a user prompt with content parts for the Ruby tracer.
Ruby tracer will support multi-modal user input in the next released version (v2.31.0).
Related dd-trace-rb PR: DataDog/dd-trace-rb#5564
Merge instructions
Should be merged when v2.31.0 of the Ruby tracer is released
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.
AI assistance
No, I have not used AI for this.
Additional notes
None.