Document automatic dataset curation for Patterns - #38560
Open
CornetVincent wants to merge 1 commit into
Open
Conversation
Contributor
|
I can only run on private repositories. |
Contributor
Preview links (active after the
|
joepeeples
approved these changes
Jul 29, 2026
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
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?
Documents the new Automatic dataset curation toggle in the Patterns configuration form. The prior flow of manually selecting a curated project and dataset has been removed in favor of a single toggle that provisions a managed project (
Patterns-coverage) and a per-pattern dataset ({pattern-name}-pattern-curated) automatically. Updating the docs keeps the Patterns setup and evaluation guidance aligned with the new UI.Source PRs:
What changed?
content/en/llm_observability/monitoring/patterns.md.How was this tested?
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Drafted with Bits Code (Datadog AI agent); prose manually reviewed for style compliance.
Additional notes
PR by Bits - View session in Datadog
Comment @DataDog to request changes