> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.42.3/advanced-topics/pattern-matching.md). # Pattern matching Elimity Insights provides several options for comparing attributes with expected values. In most cases, a simple 'equals', 'contains' or 'starts with' check is sufficient. However, from v3.24.0 onwards, users can also perform flexible pattern matching for more complex use-cases. The list below provides some example queries that were previously impossible: * find all files with a path containing at least 2 slashes: path matches pattern `/.*/` * find all users with an invalid phone number: phone does not match pattern `^\d{4}/(\d\d\.){2}\d\d$` * find all groups with a name that starts with 8 digits: name matches pattern `^\d{8}` [The Google RE2 specification](https://github.com/google/re2/wiki/Syntax) provides a technical explanation of how these patterns work exactly. For a quick overview, refer to the cheat sheet at . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.elimity.com/reference-manual/v3.42.3/advanced-topics/pattern-matching.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.