> ## Documentation Index > Fetch the complete documentation index at: https://docs.germainux.com/llms.txt > Use this file to discover all available pages before exploring further. # Search and Filters > GermainUX provides search and filtering capabilities across its dashboards, enabling users to quickly find and analyze both aggregated and raw data. Availability 8.6.0 or later > **[AI Explore](#ai-explore)** > > Ask questions in plain language > **[Full-Text Search](#full-text-search)** > > Find words, IDs and values > **[Recursive Search](#recursive-search)** > > Include parent and child events > **[Date and Time Filter](#date-and-time-filter)** > > Set global dashboard time ranges ## Features GermainUX provides search and filtering capabilities across its dashboards, enabling users to quickly find and analyze both aggregated and raw data. Search and filters help teams: * Find specific users, sessions, errors, products, pages, transactions, or events * Focus dashboards on the data relevant to an investigation * Search across related parent and child data * Assess the business and user impact of an issue * Save frequently used filters * Share filters with other users or teams * Ask AI questions about an insight and its potential root cause Search criteria and filters remain part of the analytical context as users move from high-level dashboards to individual events and Session Replay. ## AI Explore AI Explore provides a conversational, ChatGPT-like interface within the Analysis Dashboard. Instead of manually examining every chart, segment, related KPI, and instance, users can ask questions about the data being analyzed. AI Explore can help: * Explain an insight * Summarize what changed * Determine whether a KPI is abnormal * Identify affected users, sessions, pages, products, or processes * Investigate relationships between KPIs * Interpret Leading Factors > **Show all 9** > > * Suggest potential root causes > * Recommend corrective actions > * Summarize the available evidence Example questions include: * Why are Salesforce clicks slower than usual? * Which users and pages are most affected? * What changed at the same time as the slowdown? * What is the likely root cause? * Why are customers encountering errors during Shopify checkout? * Which products, devices, or customer segments are most affected? * What actions could reduce checkout abandonment? AI Explore uses the current Analysis Dashboard context, including the selected KPI, time range, filters, related KPIs, segmentation, and available instance data. ### Example: Slow Salesforce Clicks AI Explore can analyze a slow Salesforce User Click KPI and help explain: * Whether the slowdown is abnormal * Which pages or actions are affected * Which users and sessions experience it * Whether errors or HTTP requests increased at the same time * Whether the bottleneck is associated with the browser, network, or backend service * Which corrective actions should be investigated ![Search and Filters: Example: Slow Salesforce Clicks](https://mintcdn.com/germain-ux/BTxCucYnGj_ffpsA/images/main/search-and-filters/image-20260424-202944.png?fit=max\&auto=format\&n=BTxCucYnGj_ffpsA\&q=85\&s=ac2c659aabb6acae52e4b6699bcb3873) ### Example: Shopify Checkout Errors AI Explore can analyze a Shopify checkout error and help identify: * The affected checkout step * The products or variants involved * The devices, browsers, or customer segments affected * Related errors or performance problems * The likely cause of abandonment * Recommended actions to improve conversion ![Search and Filters: Example: Shopify Checkout Errors](https://mintcdn.com/germain-ux/BTxCucYnGj_ffpsA/images/main/search-and-filters/image-20260821-193516.png?fit=max\&auto=format\&n=BTxCucYnGj_ffpsA\&q=85\&s=ab2a4fd2a33b6f279421b3f82847718e) ## Full-Text Search Full-Text Search allows users to enter words, phrases, identifiers, or values to find matching data. Search can be used to find information such as: * Error messages * Usernames * Session IDs * Correlation IDs * Product names * Page titles > **Show all 13** > > * URLs > * Application names > * Server names > * Database names > * Component names > * Business-process values > * Any other collected text or metadata For example: ```text theme={null} product abc ``` ```text theme={null} error 123 ``` ```text theme={null} Salesforce ``` ```text theme={null} checkout failed ``` ### Search Values Containing Operators GermainUX supports operators such as: | Operator | Symbol | | - | - | | Equals | `==` | | Not equals | `!=` | | Less than | `<` | | Greater than | `>` | | Less than or equal | `<=` | | Greater than or equal | `>=` | If the value being searched contains a colon or another search operator, enclose the complete value in single or double quotation marks. Examples: ```text theme={null} 'Error: checkout failed' ``` ```text theme={null} "duration >= 5" ``` Quoting the value ensures that GermainUX treats it as text instead of interpreting part of it as a search operator. ![Search and Filters: Search Values Containing Operators](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-193611.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=2a45339bdc6a1eb27ca1a0824afe33df) ## Recursive Search Recursive Search searches not only the selected data but also its related parent and child data. This is particularly useful when the value being searched is contained in a related event rather than directly in the primary KPI displayed on the dashboard. For example, Recursive Search can help answer: * How many users ordered `product abc`? * Which sessions encountered `error 123`? * Which user actions generated a particular HTTP request? * Which transactions were associated with a specific backend error? * How many users were affected by a particular technology issue? * Which sessions included a specific page, popup, message, or workflow step? ### Example: Find Users Who Ordered a Product To find users who ordered `product abc`: **1. Open the relevant Drill-through Dashboard** **2. Search for `product abc`** **3. Enable or use Recursive Search to search related parent and child data** **4. Review the matching transactions, users, and sessions** **5. Open the associated Session Replays to watch the users complete the order** ### Example: Find Sessions Affected by an Error To find sessions containing `error 123`: **1. Open the relevant Drill-through Dashboard** **2. Search for `error 123`** **3. Search recursively across related events** **4. Review the matching users, sessions, and transactions** **5. Open Session Replay to see when the error appeared and how the user responded** Recursive Search connects technical, business, workflow, and user-experience data, making it easier to assess the full impact of an issue. Example of a R \ ecursive Search from Drillthrough Dashboard to Session Replay - GermainUX ![Search and Filters: Example: Find Sessions Affected by an Error](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-193645.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=d66ece3d6556c8937d6ed428a3a57cde) ## Date and Time Filter Use the Time filter to define the period displayed on a dashboard. ![Search and Filters: Date and Time Filter](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-193823.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=0f665272fe30f84398d5babe71408dca) When applied at the dashboard level, the selected time range applies globally to all portlets on that dashboard. Time ranges can be used to: * Investigate a specific incident * Compare recent performance with a prior period * Analyze a release or deployment window * Review daily, weekly, monthly, or longer-term trends * Limit an investigation to the period surrounding a user action * Exclude irrelevant historical data Preconfigured and custom time ranges can be managed under: **Settings > System > Time Ranges** ### Time Zone The selected time zone determines how dates and times are displayed and interpreted throughout GermainUX. ![Search and Filters: Time Zone](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-193844.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=807415d230887107a1e889566671ff63) Using the correct time zone is important when: * Investigating an incident * Comparing data with application or server logs * Reviewing a Session Replay * Correlating user activity with backend transactions * Sharing findings with teams in different locations Confirm the applicable time zone before comparing GermainUX data with external systems. ## Data and Metadata Filters GermainUX can filter on data and metadata collected from monitored applications, users, transactions, infrastructure, and business processes. ![Search and Filters: Data and Metadata Filters](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-193900.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=0f3775262ea8a64363c265c189888fbc) ![Search and Filters: Data and Metadata Filters, image 2](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-193910.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=75678c968241f33783399be13e630ae4) Available fields depend on the selected KPI and collected data. Examples include: * Application * Environment * Server * Host * User * Team > **Show all 21** > > * Session > * Component > * Database > * Page > * Screen > * URL > * Product > * Process > * Transaction > * Error > * Device > * Browser > * Version > * Region > * Any other collected attribute Filters can include or exclude values to focus an investigation on the relevant population. For example, users can filter data to: * Display only production activity * Exclude known or irrelevant errors * Analyze a specific application version * Focus on one user group * Compare activity across regions * Isolate a product or checkout step * Review one server or application component * Identify sessions affected by a specific error ## Count and Percentage per KPI Filter values display their count and percentage for the selected KPI whenever available. These indicators show: * How many matching instances contain the value * What percentage of the selected KPI data the value represents Count and percentage help users understand the reach of a value before applying it as a filter. For example, they can help determine whether: * An error affects most transactions or only a small subset * A browser version represents a significant portion of users * A page accounts for most slow actions * A product contributes heavily to conversion loss * A problem is isolated or widespread ![Search and Filters: Count and Percentage per KPI](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-194042.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=5a776c80511342f23ff45a8e2cea6316) ![Search and Filters: Count and Percentage per KPI, image 2](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-194052.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=2a30c585f49a44104986bdae180b9297) ## Save a Filter Frequently used filter combinations can be saved as Filter Groups. ![Search and Filters: Save a Filter](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-194000.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=982f6ae1425f36dbf30aeb10aa468720) ![Search and Filters: Save a Filter, image 2](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-194017.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=05691afb0dee4ef646e46ab7f9c3c707) A saved filter can be: * **Private:** Available only to the user who created it * **Public:** Available to other authorized users or teams Saved filters are useful for recurring investigations, operational views, application-specific analysis, and standardized team workflows. Examples include: * Production users only * Critical Salesforce errors * Shopify checkout sessions * One business unit or region * Exclusion of known non-actionable errors * A specific application and version * High-impact user sessions ## Filter Management The Filter Management screen allows authorized GermainUX administrators to centrally manage saved filters. ![Search and Filters: Filter Management](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-194112.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=46f4655ad24b480810d22fddb9a24919) Go to: **Settings > System > Filters** Administrators can use this screen to: * Review private and public filters * Update filter definitions * Enable or disable filters * Change filter availability * Maintain filters used by different teams * Remove filters that are no longer required Only users with the appropriate **UI Admin** or **Config Admin** permissions can edit public filters. Regular users can edit only the filters they own. ![Search and Filters: Filter Management, image 2](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-194125.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=b129025aa7cded11a862848c3edf2cd9) ## Dashboard and Portlet Filters Filters can be configured at two levels. ### Dashboard-Level Filter A dashboard-level filter applies to all portlets on the dashboard. ![Search and Filters: Dashboard-Level Filter](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/search-and-filters/image-20260821-194223.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=44e00058e5be1293e8e9d51792861146) Use a dashboard-level filter when every visualization should analyze the same population or conditions. For example, a dashboard-level filter can restrict the entire dashboard to: * One application * One environment * One customer segment * One region * One business process * One period or deployment version Dashboard-level filters are generally easier to manage when the same criteria should apply throughout the dashboard. ### Portlet-Level Filter A portlet-level filter applies only to one visualization. Use a portlet-level filter when a specific portlet requires different inclusion or exclusion criteria from the rest of the dashboard. For example, a portlet-level filter can: * Include only critical errors * Exclude hundreds of known or irrelevant error types * Focus on one transaction * Display only abandoned sessions * Analyze one product category * Isolate a specific user action Portlet-level filters allow individual visualizations to remain focused without changing the other portlets on the dashboard. ## Get Help > **[Contact GermainUX Support](/main/support.md)** > > The Germain Team can help you set this up. > **Can't find what you need?** > > Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing. The content of this document is proprietary to GERMAIN SOFTWARE. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.