From dc86cd750ed2558d829f0b1ed1336b57eef79584 Mon Sep 17 00:00:00 2001 From: "Kim (Sumo Logic)" <56411016+kimsauce@users.noreply.github.com> Date: Mon, 6 Oct 2025 19:15:25 -0400 Subject: [PATCH 1/2] Revert "Mobot limitation - handling query outputs (#5865)" This reverts commit f683c75f38cc066f189f70aada2d7f3412f8c7f0. --- docs/search/mobot-multiturn-beta.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/search/mobot-multiturn-beta.md b/docs/search/mobot-multiturn-beta.md index e5b389c962..3386c19fa5 100644 --- a/docs/search/mobot-multiturn-beta.md +++ b/docs/search/mobot-multiturn-beta.md @@ -136,7 +136,6 @@ Here are some common cases: * RAG only considers dashboards that have been opened in the last 90 days when interpreting your query. * Very large or highly complex queries may time out or trigger structured fallback responses. * The conversational experience is available for log-based searches only. Metrics and Metric Searches are not supported in this Beta. -* Mobot cannot currently refer to the output of a log search directly in subsequent queries. Each follow-up must be expressed in terms of query refinements rather than referencing previous results. This is an important limitation to be aware of when constructing multi-turn conversations. ## Additional resources From 7ae44c90aadb81d3e40b3c18f7c5fc481820c78f Mon Sep 17 00:00:00 2001 From: Kim Pohas Date: Mon, 6 Oct 2025 16:19:52 -0700 Subject: [PATCH 2/2] remove colons in best practices 301 links; not supported by panethon --- cid-redirects.json | 2 -- docs/search/mobot-multiturn-beta.md | 1 + 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/cid-redirects.json b/cid-redirects.json index 0db1bc8257..13e0df427c 100644 --- a/cid-redirects.json +++ b/cid-redirects.json @@ -96,8 +96,6 @@ "/03Send-Data/01-Design-Your-Deployment": "/docs/send-data/choose-collector-source", "/03Send-Data/01-Design-Your-Deployment/Best-Practices%3A-Good-Source-Category%2C-Bad-Source-Category": "/docs/send-data/best-practices", "/03Send-Data/01-Design-Your-Deployment/Best-Practices%3A-Local-and-Centralized-Data-Collection": "/docs/send-data/best-practices", - "/03Send-Data/01-Design-Your-Deployment/Best-Practices:-Good-Source-Category,-Bad-Source-Category": "/docs/send-data/best-practices", - "/03Send-Data/01-Design-Your-Deployment/Best-Practices:-Local-and-Centralized-Data-Collection": "/docs/send-data/best-practices", "/03Send-Data/01-Design-Your-Deployment/Compare-Installed-and-Hosted-Collectors": "/docs/send-data/choose-collector-source", "/03Send-Data/Applications_AWS_Solution/AWS_S3_Export_App": "/docs/send-data/hosted-collectors/amazon-aws/amazon-s3-audit-source", "/03Send-Data/Collect-from-Other-Data-Sources": "/docs/send-data/collect-from-other-data-sources", diff --git a/docs/search/mobot-multiturn-beta.md b/docs/search/mobot-multiturn-beta.md index 3386c19fa5..29041706de 100644 --- a/docs/search/mobot-multiturn-beta.md +++ b/docs/search/mobot-multiturn-beta.md @@ -136,6 +136,7 @@ Here are some common cases: * RAG only considers dashboards that have been opened in the last 90 days when interpreting your query. * Very large or highly complex queries may time out or trigger structured fallback responses. * The conversational experience is available for log-based searches only. Metrics and Metric Searches are not supported in this Beta. +* Mobot cannot refer to the output of a log search directly in subsequent queries. Each follow-up must be expressed in terms of query refinements rather than referencing previous results. This is an important limitation to be aware of when constructing multi-turn conversations. ## Additional resources