feat(llm-obs): Patterns - array bracket notation in templates#38222
Open
GLorenzo679 wants to merge 3 commits into
Open
feat(llm-obs): Patterns - array bracket notation in templates#38222GLorenzo679 wants to merge 3 commits into
GLorenzo679 wants to merge 3 commits into
Conversation
|
Bits Code status: ✅ Done CI Auto-fix: Disabled | Enable Comment @datadog-staging to request changes |
|
I can only run on private repositories. |
Contributor
Preview links (active after the
|
evazorro
approved these changes
Jul 16, 2026
evazorro
left a comment
evazorro
left a comment
Contributor
There was a problem hiding this comment.
Thanks for updating the docs! I added a tiny suggestion (on existing language, not something you changed) for a Vale warning, but this is good to go otherwise.
| - **Which spans do you want to cluster?:** Filter by application, environment, span type, or other tags to scope the Pattern to a specific slice of traffic. | ||
| - **Sampling Rate:** The percentage of matching interactions to include. Patterns processes up to 10,000 records per run; if your filter matches more than that, records are randomly sampled down to the cap. | ||
| 5. Under **What should we detect Patterns on?**, enter a template that defines what gets sent to the model for analysis. Use {{variable}} syntax to reference any span field — for example, {{meta.input.value}} to analyze patterns by user input, or {{meta.span.kind}} to analyze by span kind. Click {{< ui >}}Template Examples{{< /ui >}} to see common configurations. As you type, the right panel previews matching spans and shows what percentage of interactions have values for the variables you've referenced. | ||
| 5. Under **What should we detect Patterns on?**, enter a template that defines what gets sent to the model for analysis. Use `{{variable}}` syntax to reference any span field — for example, `{{meta.input.value}}` to analyze patterns by user input, or `{{meta.span.kind}}` to analyze by span kind. To access array elements, use bracket notation: `{{meta.input.messages[0].content}}`. Click {{< ui >}}Template Examples{{< /ui >}} to see common configurations. As you type, the right panel previews matching spans and shows what percentage of interactions have values for the variables you've referenced. |
Contributor
There was a problem hiding this comment.
Suggested change
| 5. Under **What should we detect Patterns on?**, enter a template that defines what gets sent to the model for analysis. Use `{{variable}}` syntax to reference any span field — for example, `{{meta.input.value}}` to analyze patterns by user input, or `{{meta.span.kind}}` to analyze by span kind. To access array elements, use bracket notation: `{{meta.input.messages[0].content}}`. Click {{< ui >}}Template Examples{{< /ui >}} to see common configurations. As you type, the right panel previews matching spans and shows what percentage of interactions have values for the variables you've referenced. | |
| 5. Under **What should we detect Patterns on?**, enter a template that defines what gets sent to the model for analysis. Use `{{variable}}` syntax to reference any span field; for example, `{{meta.input.value}}` to analyze patterns by user input, or `{{meta.span.kind}}` to analyze by span kind. To access array elements, use bracket notation: `{{meta.input.messages[0].content}}`. Click {{< ui >}}Template Examples{{< /ui >}} to see common configurations. As you type, the right panel previews matching spans and shows what percentage of interactions have values for the variables you've referenced. |
Fixing this existing issue to solve the Vale warning!
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?
Updates
content/en/llm_observability/monitoring/patterns.mdto document that template array access requires bracket notation.Source PRs that made this change necessary: