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
Copy file name to clipboardExpand all lines: en/rum/explorer/data-query.mdx
+40Lines changed: 40 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,46 @@ description: "Master Flashduty RUM Explorer search syntax to quickly locate and
5
5
6
6
Flashduty RUM Explorer provides powerful search capabilities, allowing you to quickly locate and analyze RUM data through flexible query syntax. Queries consist of **terms** and **operators**, supporting complex search condition combinations.
7
7
8
+
## AI natural-language query
9
+
10
+
If you are not yet familiar with the query syntax, you can describe the data you want to find in plain language, and AI will convert it into a query for you.
11
+
12
+
<Steps>
13
+
<Steptitle="Enter AI query">
14
+
Click the **magic wand** icon in the query input to enter AI natural-language query mode. Once active, the input border is highlighted to clearly distinguish it from regular query mode.
15
+
</Step>
16
+
<Steptitle="Describe your intent">
17
+
Describe the data you want to find in plain language (Chinese or English supported), then press **Enter** to convert. For example:
18
+
19
+
```
20
+
5xx resource requests from Chrome that took longer than 2 seconds
AI generates the corresponding query and shows a preview. When it looks right, click **Apply** and the query takes effect immediately; if the result is not what you expected, refine your description and press Enter again to regenerate, or click **Undo** to revert to the state before applying.
31
+
</Step>
32
+
</Steps>
33
+
34
+
<Note>
35
+
AI generates a standard query (DQL) using the same fields and syntax as manual queries (see below). You do not need to remember field names — AI automatically picks the queryable fields based on the current event type.
36
+
</Note>
37
+
38
+
### Append instead of replace
39
+
40
+
When the input already contains query conditions, the AI-generated conditions are **appended** to the existing query rather than overwriting it. This lets you build on an existing query and add filters incrementally in plain language. If the query is currently empty, the generated result is applied directly.
41
+
42
+
If your description fits a different event type better, AI prompts you to switch (for example, "Switch event type to Errors") and generates the query within that event type's queryable fields.
43
+
44
+
<Tip>
45
+
Describe your intent in **plain language** in the AI input — there is no need to hand-write query syntax (such as `browser_name:Chrome`), as entering query syntax directly lowers conversion accuracy. When you need precise control over conditions, use the query syntax below instead.
0 commit comments