You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -15,11 +15,15 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
15
15
This feature is in Beta. For more information, contact your Sumo Logic account executive.
16
16
:::
17
17
18
-
Our new conversational experience in Sumo Logic Mobot (formerly known as *Copilot*) lets you interact with queries the way you would with a chat assistant. You ask a question and can refine it with follow-ups, change units, and see the updated query and visualization without starting over. Mobot maintains your intent across turns, surfaces helpful suggestions, and makes it easy to explore related angles. This guide explains what's new in the UI, how the multi-turn flow works, and shows example workflows.
18
+
Our new conversational experience in Mobot (formerly known as Copilot) lets you interact with queries the way you would with a chat assistant. You ask a question and can refine it with follow-ups, change units, and see the updated query and visualization without starting over. Mobot maintains your intent across turns, surfaces helpful suggestions, and makes it easy to explore related angles. This guide explains what's new in the UI, how the conversational flow works, and shows example workflows.
19
+
20
+
:::note Name update
21
+
We are renaming *Copilot* to *Mobot*. During the transition, some UI labels and screenshots may still show **Copilot**. Functionality is unchanged. Learn more about [Mobot](/docs/search/mobot).
22
+
:::
19
23
20
24
## What's new in Beta
21
25
22
-
***Multi-turn conversations**. Refine queries through natural, conversational follow-up questions without losing context.
26
+
***Conversational flow**. Refine queries through natural, conversational follow-up questions without losing context.
23
27
***Improved accuracy**. Translations to Sumo Query Language are more reliable, especially for data sources with active dashboards.
24
28
***Clarifications when needed**. If your request is ambiguous, Mobot may ask a follow-up question to narrow intent.
25
29
***Smarter error handling**. Instead of generic errors, Mobot provides clearer messages and fallback suggestions for next steps.
@@ -31,43 +35,43 @@ Our new conversational experience in Sumo Logic Mobot (formerly known as *Copilo
31
35
32
36
In the below example, we'll use the following key concepts:
33
37
34
-
***Multi-turn conversation**. A sequence of related instructions that retains context and incrementally updates the query and output.
38
+
***Conversational flow**. A sequence of related instructions that retains context and incrementally updates the query and output.
35
39
***Intent card**. Visual summary of what you're asking Mobot to do in this session.
36
40
***Suggestion cards**. Recommended refinements or adjacent analyses you can apply with a click.
37
41
38
-
This example workflow demonstrates the multi-turn interaction pattern; you can apply the same steps to other logs, events, or dimensions.
42
+
This example demonstrates the conversational interaction pattern; you can apply the same steps to other logs, events, or dimensions.
39
43
40
44
### Step 1: Ask your initial question
41
45
42
46
Start broad when you set a goal. We'll ask: `Show failed login attempts in the last 24 hours`.
43
47
44
48
An intent card appears in the conversation pane that summarizes your goal. Mobot also surfaces suggestion cards with related refinements you can click, and gives you the option to open the query in Log Search.
45
49
46
-
<img src={useBaseUrl('img/search/mobot/initial-question.png')} alt="Mobot multi-turn conversation showing initial query, failed login attempts in the last 24 hours" style={{border: '1px solid gray'}} width="700"/>
50
+
<img src={useBaseUrl('img/search/mobot/initial-question.png')} alt="Mobot conversational experience showing initial query for failed login attempts in the last 24 hours" style={{border: '1px solid gray'}} width="700"/>
47
51
48
52
### Step 2: Narrow the scope
49
53
50
54
The top reason in the table is `FailedScheduling`, so we'll select a follow-up suggestion, `Show failed scheduling events`. Mobot refreshes the results and updates the intent card and query to reflect the new focus.
<img src={useBaseUrl('img/search/mobot/narrow-scope-filter.png')} alt="Mobot conversational experience showing failed scheduling events broken down by namespace" style={{border: '1px solid gray'}} width="700"/>
57
61
58
62
Mobot adjusts the query, applies the refinements, and renders a visual chart.
59
63
60
64
### Step 3: Drill into causes
61
65
62
66
Next, type `Add error messages`. Mobot translates this into: `Add error messages to the breakdown of failed scheduling events by namespace`. The intent card expands to include the new scope, and results now show error message details.
Finally, type: `Show the trend over 24 hours`. Mobot translates this into: `Show the trend of failed scheduling events by namespace with error messages over 24 hours`. The query applies a timeslice (for example, one-hour buckets) to group results over time.
Mobot also presents new suggestion cards to help you pivot into related questions, such as analyzing trends of event reasons or identifying top namespaces.
73
77
@@ -87,7 +91,7 @@ You can also [edit the query logic](/docs/search/mobot/#edit-query-code), [open
87
91
88
92
## FAQ
89
93
90
-
The questions below refer specifically to the multi-turn conversion (beta) experience. For general information about Mobot, see the [Mobot FAQ](/docs/search/mobot#faq).
94
+
The questions below refer specifically to the conversational (Beta) experience. For general information about Mobot, see the [Mobot FAQ](/docs/search/mobot#faq).
91
95
92
96
<details>
93
97
<summary>Is any user or org data sent outside our environment?</summary>
@@ -119,7 +123,7 @@ Here are some common cases:
119
123
* For dashboard-aware translations via RAG, support is limited to the `sourceCategory` filter (selection in the source picker) at launch. Other expressions like `_index=` or `_sourceHost=` are not yet supported.
120
124
* RAG only considers dashboards that have been opened in the last 90 days when interpreting your query.
121
125
* Very large or highly complex queries may time out or trigger structured fallback responses.
122
-
*Multi-turn Mobot is available for log-based searches only. Metrics and Metric Searches are not supported in this Beta.
126
+
*The conversational experience is available for log-based searches only. Metrics and Metric Searches are not supported in this Beta.
Copy file name to clipboardExpand all lines: docs/search/mobot.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ import Iframe from 'react-iframe';
16
16
import useBaseUrl from '@docusaurus/useBaseUrl';
17
17
18
18
:::note Name update
19
-
We are renaming Copilot to Mobot across the product and docs. During this transition, some UI labels and screenshots may still show "Copilot". Functionality is the same. We will update names and images as the rollout completes.
19
+
We are renaming *Copilot* to *Mobot* across the product and docs. During this transition, some UI labels and screenshots may still show **Copilot**. Functionality is the same. We will update names and images as the rollout completes.
20
20
:::
21
21
22
22
Sumo Logic Mobot (formerly known as *Copilot*) is our AI-powered assistant that accelerates investigations and troubleshooting in logs by allowing you to ask questions in plain English and get contextual suggestions, helping first responders get to answers faster.
0 commit comments