From 17d19eb18f2c699ecb7281a12355a5191ac832a3 Mon Sep 17 00:00:00 2001 From: Anis Zoubir Amar Date: Fri, 3 Jul 2026 14:32:57 +0200 Subject: [PATCH 1/2] docs(llm-obs): document scheduling for Patterns configs Add a 'Schedule runs' section to the Patterns page describing the recurring cadence options (daily, weekdays, weekly, custom 1-7 days) and that scheduled runs use the same pipeline as manual runs. --- .../en/llm_observability/monitoring/patterns.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/content/en/llm_observability/monitoring/patterns.md b/content/en/llm_observability/monitoring/patterns.md index 84428c9c57f..ea4f93c1776 100644 --- a/content/en/llm_observability/monitoring/patterns.md +++ b/content/en/llm_observability/monitoring/patterns.md @@ -109,6 +109,20 @@ To analyze your production traffic, click {{< ui >}}Run analysis{{< /ui >}} in t If a run fails, a modal explains the cause and what action to take. The page continues to display results from the most recent successful run while the failed run is shown in the header. +## Schedule runs + +Instead of triggering every run manually, configure a Pattern to run automatically on a recurring schedule. + +When you create or edit a Pattern, under **How often should we run Patterns?**, choose a cadence: + +- **On demand**: No schedule. Run the Pattern manually (default). +- **Daily**: Every day at a time you choose. +- **Weekdays**: Monday through Friday at a time you choose. +- **Weekly**: A chosen day of the week at a time you choose. +- **Custom**: Every 1 to 7 days. + +Scheduled times use your Datadog timezone preference. Each scheduled run uses the same pipeline as a manual run, so results appear in the same place, and the Patterns page always shows your most recent run. + ## Use topics to improve your application ### Understand your production traffic From 11d7ab234f35d6a236f96b532482954f7486a356 Mon Sep 17 00:00:00 2001 From: Anis Zoubir Amar Date: Fri, 3 Jul 2026 14:40:32 +0200 Subject: [PATCH 2/2] docs(llm-obs): fold Patterns scheduling into the setup steps Move the schedule cadence options into 'Set up a Pattern' (a new step before Save) since configuring a schedule is part of creating a Pattern; drop the separate section to avoid duplication. --- .../llm_observability/monitoring/patterns.md | 22 ++++++------------- 1 file changed, 7 insertions(+), 15 deletions(-) diff --git a/content/en/llm_observability/monitoring/patterns.md b/content/en/llm_observability/monitoring/patterns.md index ea4f93c1776..fa2a6cd3159 100644 --- a/content/en/llm_observability/monitoring/patterns.md +++ b/content/en/llm_observability/monitoring/patterns.md @@ -55,7 +55,13 @@ Each topic shows its interaction volume and share of total traffic. Interactions - **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. -6. Click **Save** +6. Under **How often should we run Patterns?**, choose how the Pattern runs: + - **On demand** (default): Run the Pattern manually. + - **Daily**, **Weekdays**, or **Weekly**: Run automatically at a time (and, for weekly, a day) you choose. + - **Custom**: Run automatically every 1 to 7 days. + + Scheduled times use your Datadog timezone preference. Scheduled runs use the same pipeline as a manual run, so results appear in the same place, and the Patterns page always shows your most recent run. +7. Click **Save** ## Explore your Patterns @@ -109,20 +115,6 @@ To analyze your production traffic, click {{< ui >}}Run analysis{{< /ui >}} in t If a run fails, a modal explains the cause and what action to take. The page continues to display results from the most recent successful run while the failed run is shown in the header. -## Schedule runs - -Instead of triggering every run manually, configure a Pattern to run automatically on a recurring schedule. - -When you create or edit a Pattern, under **How often should we run Patterns?**, choose a cadence: - -- **On demand**: No schedule. Run the Pattern manually (default). -- **Daily**: Every day at a time you choose. -- **Weekdays**: Monday through Friday at a time you choose. -- **Weekly**: A chosen day of the week at a time you choose. -- **Custom**: Every 1 to 7 days. - -Scheduled times use your Datadog timezone preference. Each scheduled run uses the same pipeline as a manual run, so results appear in the same place, and the Patterns page always shows your most recent run. - ## Use topics to improve your application ### Understand your production traffic