Query Basics
Queries support two types of terms:Boolean Operators
AI Natural-Language Queries
When you do not want to write DQL by hand, let AI turn a natural-language request into query conditions. In the RUM Explorer query field, click the AI Natural-Language Query icon on the left. You can also press ⌘ + Enter from the normal query mode, or Ctrl + Enter on Windows and Linux.1
Describe what you want to find
Use natural language, such as “errors on Chrome,” “resource requests slower than 2 seconds,” or “checkout pages from the last 24 hours.” Press Enter to generate a preview.
2
Review the preview
The preview shows the DQL condition to add. When the request better fits another event type or time range, it also shows the event-type or time-range change.
3
Apply or undo
Click Apply, Append to Query, or Switch and Apply to confirm the change. After applying it, the confirmation message offers Undo to restore the previous query, event type, and time range.
Time expressions such as “last hour,” “yesterday,” and “past 7 days” update the Explorer time picker; they are not written as DQL conditions such as
client_time. Performance-duration conditions remain DQL, for example view_loading_time:>2s.Full-Text Search
Escape Special Characters
When searching for field values containing special characters, you need to escape them with backslash\ or use double quotes.
The following characters are considered special:
:, ", *, -, >, <, ,, (, ), [, ], \ and spaceAttribute Search
Useattribute:term syntax to search specific attributes:
Numeric Search
For numeric type attributes, comparison operators can be used:Complex Query Examples
- Error Analysis
- Performance Analysis
- Error Requests
- Page Behavior
Search for Warning type errors that occurred in the wallet page:
WeChat Mini Program-Specific Attributes
For View events collected from the WeChat Mini Program platform, the following queryable attributes are available in addition to the sharedview_* fields. They help diagnose cold-start latency, setData cost, and lifecycle-stage durations:
For example, to find Mini Program pages with a first-screen render longer than 2 seconds:
Advanced Search Tips
Time Range Search
Time Range Search
Perform precise searches combined with time range:
User Behavior Search
User Behavior Search
Search for user click behavior on the checkout page:
Device Type Search
Device Type Search
Search for views with loading time over 3 seconds on mobile devices:
Geographic Location Search
Geographic Location Search
Search for sessions with errors in China region:
Best Practices
Use Quotes for Phrases
Ensure exact matching of multi-word phrases
Use Wildcards Wisely
Avoid overly broad search conditions
Combine Multiple Conditions
Build precise queries through AND/OR operators
Use Auto-Complete
Reduce input errors and improve search accuracy
Next Steps
RUM Explorer Overview
Learn about Explorer core features
Distributed Tracing
Learn distributed tracing best practices