Query
Download
Focus Mode
Font Size
This article aims to explain tips on using the search feature in pages such as the issue list and issue details.
Manage filter fields
Expand filter options and collapse filter options
After opening the page, by default, it is in the collapsed state. You can click Display filter to display all added filter fields.
Edit the field
By default, all filter fields supported on the current page are displayed. Users can click Edit Field to freely adjust the fields they wish to display.
Note:
After the user adjusts the displayed filter options, the platform saves the user's settings locally in the browser. If the cache is not cleared, the next time they go to the same page, the fields displayed are those set last time.
Search
After adjusting the filter fields, the search does not take effect immediately; you need to manually click Retrieve to actually execute the search operation.
Reset
You can clear all filter options by clicking Reset on the page.
Filter Field Type
The filter options supported by the platform can be categorized into these types: Time Range, Version Type, Numeric Type, String Type, String Array Type, Enumerable Type, Special Type. Different types support different search modes, with most search modes supporting multiple keywords. Below are detailed descriptions of these filter types.
Time Range
Time Range supports five aggregation granularities: 5-minute, hour, day, week, and month.
Among these, 5-minute and hourly aggregations only support data from the last 48 hours, including custom, Last 1 Hour, Today, and Yesterday modes.
The day, week, and month aggregation granularities support modes such as custom, Last 7 Days, Last 30 Days, Last 45 Days and last 90 days.
Edition type
The version type fields include filter fields such as App version, SDK version, and system version. They support Yes, No, Greater than, Greater than or equal to, Less than, Less Than or Equal to, interval, Match, Not Matched, Empty, Not Empty, Match at the beginning, Beginning mismatch, Ends With Match, End mismatch, and Regular Expression search modes.
Version type fields essentially store a string that conforms to version specifications. Therefore, version type filter options possess all search modes available for both numeric type and string type filter options.
Version Comparison:
The platform follows industry-recommended version formats, i.e., "major.minor.patch.build". It first parses the version field and normalizes it into four parts (A.B.C.D), padding with zeros if fewer than four components exist. Version comparison follows the priority rule: major version (A) > minor version (B) > patch (C) > build (D). For example: "4.5.2.1" > "4.5.2.0" > "4.5.1.99" > "4.4.2.100". This parsing and comparison logic also applies to system versions, e.g., "Android 7.1.2,level 25" > "Android 6.0.1,level 23" > "Android 5.1,level 22" > "Android 5.0.2,level 21".
Here are the detailed comparison rules:
1. When determining priority levels, the version must (MUST) be split into major version, minor version, patch version, and pre-release version in sequence for comparison (build metadata is not included in this comparison list).
2. Compare each component from left to right sequentially, and the first differing value determines the priority level: major version, minor version, and patch version are compared numerically. For example: 1.0.0 < 2.0.0 < 2.1.0.
3. When the major version, minor version, and patch are identical, pre-release versions have lower priority. For example: 1.0.0-alpha < 1.0.0.
4. When two pre-release versions share the same major, minor, and patch versions, their priority level (MUST) be determined by comparing dot-separated identifiers from left to right until a difference is found:
Numeric identifiers are compared numerically.
When identifiers contain letters or hyphens, they are compared lexically in ASCII sort order.
Numeric identifiers have lower priority than non-numeric identifiers.
If the initial identifiers are identical, the pre-release version with more fields has higher priority. For example: 1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0.
Search Mode | Description |
Yes | Exact string comparison supports input of multiple keywords in an OR relationship, meaning the condition is satisfied when the field's value equals any one of the input keywords. |
No | Exact string comparison supports input of multiple keywords in an AND relationship, meaning the condition is satisfied when the field's value does not equal any of the input keywords. |
Greater than/Greater than or equal to | Version comparison only allows one keyword as input, indicating that the condition is satisfied when the field's value is greater than / greater than or equal to the version represented by the input keyword. |
Less than/Less Than or Equal to | Version comparison only allows one keyword as input, indicating that the condition is satisfied when the field's value is less than / less than or equal to the version represented by the input keyword. |
interval | Version comparison requires input of two keywords, for example, if the input keywords are A and B, the condition is satisfied when A <= x <= B. |
Empty | When the field is an empty string / or when the corresponding field is not reported, the condition is satisfied. The platform does not distinguish between no value and an empty string. |
Not empty | The condition is satisfied when the field is a non-empty string, that is, when the string length is greater than 0. |
Match | Fuzzy string matching supports input of multiple keywords in an OR relationship, meaning the condition is satisfied when the field's value contains any one of the input keywords. |
Not Matched | Fuzzy string matching supports input of multiple keywords in an AND relationship, meaning the condition is satisfied when the field's value does not contain any of the input keywords. |
Match at the beginning | Fuzzy string matching supports input of multiple keywords in an OR relationship, meaning the condition is satisfied when the field's value starts with any of the input keywords. |
Does not start with | Fuzzy string matching supports input of multiple keywords in an AND relationship, meaning the condition is satisfied when the field's value does not start with any of the input keywords. |
Ends With Match | Fuzzy string matching supports input of multiple keywords in an OR relationship, meaning the condition is satisfied when the field's value ends with any of the input keywords. |
End mismatch | Fuzzy string matching supports input of multiple keywords in an AND relationship, meaning the condition is satisfied when the field's value does not end with any of the input keywords. |
Regular Expression | Fuzzy string matching supports input of multiple keywords in an OR relationship, meaning the condition is satisfied when the field's value matches any of the input keywords. |
The following demonstrates version type searches through several examples of App version.
Search Purpose | operator | Input keyword | Description |
Search for instances with versions greater than '4.5.2'. | Greater than | '4.5.2' | Instances with version '4.5.2.1' satisfy the condition, but those with version '4.5.2.0' do not. |
Search for instances of all subversions for versions '4.5.2' and '4.5.3'. | Starts with | '4.5.2.', '4.5.3.' | If the trailing '.' is omitted, versions such as '4.5.20.xx' and similar will also be included. |
Search for instances of all subversions with hotpatch version 499. | Ends with | '(hotpatch:499)' | The App version consists of a major version number and a hotpatch version number, represented in the standard format: '4.5.3.1(hotpatch:499)', where '4.5.3.1' is the major version number. |
Value Type
Filter items of numerical type include fields such as Usage Duration, Available memory, and Lag time. Supported search modes are Equal to, Not equal to, Greater than, Greater than or equal to, Less than, Less Than or Equal to, and interval.
Filter items of numerical type store values that are either integers or floating-point numbers.
Search Mode | Meaning |
Equal to | It supports entering multiple keywords, which are in an OR relationship, meaning the condition is met when the field value equals any one of the input keywords. |
Not equal to | It supports entering multiple keywords, which are in an AND relationship, meaning the condition is met when the field value does not equal any one of the input keywords. |
Greater than | Only a single keyword input is supported, indicating that the condition is met when the field value is greater than the input keyword. |
Greater than or equal to | Only a single keyword input is supported, indicating that the condition is met when the field value is greater than or equal to the input keyword. |
Less than | Only a single keyword input is supported, indicating that the condition is met when the field value is less than the input keyword. |
Less Than or Equal to | Only a single keyword input is supported, indicating that the condition is met when the field value is less than or equal to the input keyword. |
interval | It supports entering two keywords, such as left and right, indicating that the condition is met when the field value equals either of them or falls between them. |
The following demonstrates numeric search through several examples of Usage Duration.
Search Purpose | operator | Input keyword | Description |
Search for cases where the Usage Duration is greater than 30 seconds | Greater than | 30 | The unit of usage duration is seconds, so entering 30 indicates 30 seconds. |
Search for cases where the Usage Duration is between 30 minutes and 1 hour | Interval | 1800, 3600 | The unit of usage duration is seconds, where 30 minutes equals 1800 seconds, and 1 hour equals 3600 seconds. |
The following demonstrates numeric search using the custom dimension field n1. Assume that the business uses n1 to represent the tier classification of device models, divided into five tiers ranging from 1 to 5 (lowest to highest).
Search Purpose | operator | Input keyword | Description |
Search for cases reported by models of tier 1 and tier 2 | Yes | 1,2 | Indicates searching for cases where n1 = 1 or n1 = 2 |
Search for cases reported by models of tiers other than 1 and 3 | No | 1, 3 | Indicates searching for cases where n1 != 1 and n1 != 3 |
Search for cases reported by models of tier 3 and above | Greater than or equal to | 3 | Indicates searching for cases where n1 >= 3 |
Search for cases reported by models of tier 2 to tier 4 | Interval | 2, 4 | Indicates searching for cases where 2 <= n1 <= 4 |
String Type
Supports Yes, No, Match, Not Matched, Match simultaneously, Empty, Not Empty, Match at the beginning, Beginning mismatch, Ends With Match, End mismatch, Regular expression match, Regular expression mismatch search modes.
String-type filter options include error stack, faulty thread, faulty process, Message ID, Device ID, User ID, Scene, Model, Vendor, etc.
Search Mode | Meaning |
Yes | Exact string comparison supports input of multiple keywords in an OR relationship, meaning the condition is satisfied when the field's value equals any one of the input keywords. |
No | Exact string comparison supports input of multiple keywords in an AND relationship, meaning the condition is satisfied when the field's value does not equal any of the input keywords. |
Empty | When the field is an empty string / or when the corresponding field is not reported, the condition is satisfied. The platform does not distinguish between no value and an empty string. |
Not Empty | The condition is satisfied when the field is a non-empty string, that is, when the string length is greater than 0. |
Match | Fuzzy string matching supports input of multiple keywords in an OR relationship, meaning the condition is satisfied when the field's value contains any one of the input keywords. |
Match simultaneously | Fuzzy string matching supports input of multiple keywords in an AND relationship, meaning the condition is satisfied when the field's value contains all of the input keywords. |
Not Matched | Fuzzy string matching supports input of multiple keywords in an AND relationship, meaning the condition is satisfied when the field's value does not contain any of the input keywords. |
Match at the beginning | Fuzzy string matching supports input of multiple keywords in an OR relationship, meaning the condition is satisfied when the field's value starts with any of the input keywords. |
Begingning mismatch | Fuzzy string matching supports input of multiple keywords in an AND relationship, meaning the condition is satisfied when the field's value does not start with any of the input keywords. |
Ends With Match | Fuzzy string matching supports input of multiple keywords in an OR relationship, meaning the condition is satisfied when the field's value ends with any of the input keywords. |
End mismatch | Fuzzy string matching supports input of multiple keywords in an AND relationship, meaning the condition is satisfied when the field's value does not end with any of the input keywords. |
Regular expression match | Fuzzy string matching supports input of multiple keywords in an OR relationship, meaning the condition is satisfied when the field's value matches any of the input keywords. |
Regular expression mismatch | Fuzzy string matching supports input of multiple keywords in an AND relationship, meaning the condition is satisfied when the field's value does not match any of the input keywords. |
The following demonstrates string search through several samples of stack trace.
Search Purpose | operator | Input keyword | Description |
Search for stack trace instances that contain the package name 'com.tencent.rumpro'. | Match | 'com.tencent.rumpro' | Stacks typically contain multiple function frames, where containment matching is required rather than prefix matching. |
Search for stack trace instances that contain both the 'com.tencent.rumpro' and 'com.tencent.rmonitor' package names. | Simultaneous match | 'com.tencent.rumpro', 'com.tencent.rmonitor' | Simultaneous matching indicates that the stack trace must contain all specified keywords. |
The following uses several examples of error process to demonstrate string search. Assume a business contains multiple processes, as detailed below:
Business processes | Process Type |
com.tencent.demo | Main process |
com.tencent.demo:video_1 | Video processes |
com.tencent.demo:video_2 | Video processes |
com.tencent.demo:game_1 | Game processes |
com.tencent.demo:game_2 | Game processes |
com.tencent.demo:xg_vip_service | Service processes |
com.tencent.demo:pm_service | Service processes |
com.tencent.demo:decode_service | Service processes |
com.tencent.demo:encode_service | Service processes |
Search Purpose | operator | Input keyword | Description |
Search for the instances that only appear in the main process. | Yes | com.tencent.demo | Adopting exact match of field values |
Search for the instances that only appear in the video process. | Starts with | com.tencent.demo:video_ | Find the video process by prefix matching. |
Search for the instances that appear in the video process or game process. | Starts with | com.tencent.demo:video , com.tencent.demo:game | By entering multiple keywords to achieve the desired effect. |
Search for the instances that do not appear in the service processes. | Does not end with | _service | Search for instances not occurring in service processes through suffix mismatch. |
String array type
The string array type indicates that the value of a field is a string array, including fields such as custom dimension's a1-a10, experiment ID, Tag for individual case, business drill-down.
The string array type supports search patterns such as Include, Exclude, contains both, Match, Match simultaneously, Empty, Not Empty, Match at the beginning, Ends With Match, and others. For the comparison of string arrays, most patterns ultimately compare each string in the string array.
Search Mode | Meaning |
Include | Exact string comparison supports inputting multiple keywords, which are in an OR relationship, meaning the condition is met when any of these keywords is present in the field value. |
Exclude | Exact string comparison supports inputting multiple keywords in an AND relationship, meaning the condition is met only when none of the keywords are present in the field value. |
contains both | Exact string comparison supports inputting multiple keywords in an AND relationship, meaning the condition is met only when all keywords are present in the field value. |
Match | Fuzzy string comparison supports inputting multiple keywords in an OR relationship, meaning the condition is met when any string in the field value contains any of the input keywords. |
Match simultaneously | Fuzzy string comparison supports inputting multiple keywords in an AND relationship, meaning the condition is met when any string in the field value contains all input keywords. |
Empty | The condition is met when the field value is an empty array. |
Not Empty | The condition is met when the field value is not an empty array. |
Match at the beginning | Fuzzy string comparison supports inputting multiple keywords in an OR relationship, meaning the condition is satisfied when any string in the field value starts with any of the input keywords. |
EndsWith Match | Fuzzy string comparison supports inputting multiple keywords in an OR relationship, meaning the condition is satisfied when any string in the field value ends with any of the input keywords. |
For example, a user uses the a1 field to report the names of recently visited pages. The login page contains two Models: 'LoginModeOnePage' and 'LoginModeTwoPage'. Below are some examples of the a1 field values reported.
Reported Cases | a1 field value |
1 | ['LoginModeOnePage', 'MessageListPage', 'FriendDetailPage'] |
2 | ['LoginModeTwoPage', 'MessageListPage', 'FriendListPage'] |
3 | ['LoginModeTwoPage', 'MessageListPage', 'FriendListPage', 'FriendDetailPage'] |
4 | ['MessageListPage', 'FriendListPage', 'FriendDetailPage'] |
5 | ['FriendListPage', 'MessageListPage', 'FriendDetailPage'] |
Below are several examples of custom dimension a1 to demonstrate string array type search.
Search Purpose | operator | Input keyword | Description |
Search for cases that include the login page, such as cases 1, 2, and 3 mentioned above. | Include | 'LoginModeOnePage', 'LoginModeTwoPage' | The login page contains two Models: 'LoginModeOnePage' and 'LoginModeTwoPage'. |
Search for cases that include the login page, such as cases 1, 2, and 3 mentioned above. | Starts with | 'Login' | Using 'Login' to match the two Models of the login page. |
Search for cases that include both the login page and the friend detail page, such as cases 1 and 3 mentioned above. | Simultaneous match | 'Login','FriendDetailPage' | Here, simultaneous inclusion cannot be used because 'LoginModeOnePage' and 'LoginModeTwoPage' do not appear at the same time. |
Search for cases that have not performed login operations, such as cases 4 and 5 mentioned above. | Not included | 'LoginModeOnePage', 'LoginModeTwoPage' | Not included is the negation of included. |
Enumerable Type
Enumerated types are multi-select dropdown boxes that include "All" and all available options for the field. Filter options for enumerated types include fields such as build type, Foreground or background status, and Device Type.
Enumerated types may store boolean values, strings, or integers. Regardless of the type, enumerated types are always those with enumerable values, and the number of distinct values is typically not excessive—generally not exceeding 10 items.
Enumerated types default to "All selected," meaning no filtering by any specific type. Users can select the types to match via the dropdown, which typically supports multiple selection.
Filter Field | Enum value |
build type | All, Developer Edition, Canary Edition, Release Edition |
Foreground or background status | All, Foreground, Background |
Device Type | Real Device + Simulator, Real Device, Simulator |
The following demonstrates the search for enumerated types through several examples of Edition Type.
Search Purpose | Selected items | Description |
Search all reported cases in the Developer Edition. | Developer Edition | This indicates that only cases in the Developer Edition will be searched. |
Search for reported cases in the Canary Edition and Release Edition. | Canary Edition, Release Edition | This indicates that the condition is met as long as it is one of the Canary Edition or Release Edition types. |
Search for all reported cases in all editions. | No limit | When the "No limit" option is selected, no other options can be chosen simultaneously. |
Special Type
Special type filter options support two search modes: OR, AND, including fields such as linkage marking, exception site, attachment.
Search Mode | Meaning |
OR | It supports selecting multiple options, which are in an OR relationship. |
AND | It supports selecting multiple options, which are in an AND relationship. |
The following demonstrates special type searches through several samples of linkage marks in the crash issue list.
Search Purpose | operator | Input keyword | Description |
Search for cases where lag or Java memory leaks occurred before a crash. | OR | Lag, Java memory leak | The condition is met as long as the case has experienced lag or Java memory leak. |
Search for cases where both lag and Java memory leaks occurred before a crash. | AND | Lag, Java memory leak | Only cases where both lag and Java memory leaks have occurred meet the condition. |
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback