--- title: "Search best practices" slug: "search-best-practices-1" tags: ["Helix", "Sec Ops and Analytics", "Product Usage"] updated: 2026-09-13T08:42:40Z published: 2026-09-13T08:42:40Z canonical: "docs.trellix.com/search-best-practices-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Search best practices - Use a list and refer to it instead of repeatedly using arrays. - Regular expression (regex) operations can be performed against a maximum of 50,000 events for each search in Helix. To perform regex operations against larger datasets, you must filter search results to fewer than 50,000 events. Otherwise, the search will not complete successfully. - Encapsulate all string patterns with single or double quotation marks to help ensure that Helix accurately interprets the string. For example: - Using spaces and special characters within a `rawmsg` string pattern can result in inconsistent search results. To avoid this, either encapsulate single words with quotation marks as noted above or use the `AND` operator between words. For example: - `count>"4"` - `eventtime>'2022-04-07T01:10:50:000Z'` - Using spaces and special characters within a `rawmsg` string pattern can result in inconsistent search results. To avoid this, either encapsulate single words with quotation marks as noted above or use the `AND` operator between words. For example: - Use `"incapsula" AND "impreva"` instead of `"incapsula impreva"`. - Use `'username' 'admin'` instead of `'username:admin'`. - Using `:` (contains) instead of `=` (exact match) is recommended for inexperienced users.