Log Search Query Syntax | MuleSoft Documentation
# Log Search Query Syntax
In addition to using the query builder and facet search user interface in Runtime Manager log search, you can use the log search query language.
## Search Terms
Search terms consist of terms and operators. Search terms can be either single terms, such as "hello" or phrases, such as "hello dolly".
You can combine multiple terms with boolean operators to form complex queries.
## Term Modifiers
You can modify query terms using the log search query language to provide a wide range of searching options.
## Wildcard Searches
You can use single and multiple character wildcard searches within single terms.
To perform a single character wildcard search use the `?` symbol. The single character wildcard search looks for terms that match the single character replaced by `?`. For example, to search for "text" or "test" you can use the search:
To perform a multiple-character wildcard search, use the * symbol. Multiple-character wildcard searches look for zero or more characters. For example, to search for test, tests, or tester, use the search:
You can also use the wildcard searches in the middle of a term, for example: `te*t`.
## Boolean Operators
Boolean operators allow terms to be combined through logic operators. Log search query language supports `AND`, `+`, `OR`, `NOT` and `-` as Boolean operators.
Boolean operators must be ALL CAPS.   
---  
Boolean Operator | Description | Example  
---|---|---  
The `AND` operator matches documents where both terms exist anywhere in the text of a single document. This is equivalent to an intersection using sets. |  To search for documents that contain "anypoint monitoring" use the query: `"anypoint monitoring" AND "results"`  
The `OR` operator is used by default if there is no Boolean operator inserted between two terms. The `OR` operator links two terms and returns a matching document if either of the terms exists in a document. This is equivalent to a union using sets. The symbol `| |` can be used in place of the word `OR`. |  To search for documents that contain either "monitoring anypoint" or just "monitoring" use the query: `"monitoring anypoint" monitoring` `"monitoring anypoint" OR monitoring`  
The `NOT` operator excludes documents that contain the term after `NOT`. This is equivalent to a difference using sets. The symbol `!` can be used in place of the word `NOT`. |  To search for documents that contain "anypoint monitoring" but not "functional", use the query: `"anypoint monitoring" NOT "functional"` |  The `NOT` operator can’t be used with just one term. For example, the following search returns no results: `NOT "functional"`  
---  
Requires that the term after the `+` symbol exists somewhere in the field of a single document. |  To search for documents that must contain "anypoint" and may contain "monitoring" use the query: `+anypoint monitoring`  
Excludes documents that contain the term after the `-` symbol. |  To search for documents that contain "anypoint monitoring" but not "results" use the query: `"anypoint monitoring" -"results"`  
## Special Characters
You can escape special characters that are part of the query syntax. The current list of supported special characters includes:
`+ - && || ! ( ) { } [ ] ^ " ~ * ? : \ < >`
To escape these characters, use the `\` before the character. For example, to search for (1+1):2 use the query:
`\(1\+1\)\:2`
## Search Fields
Specify a field name or use the default when performing a search. The field name and default field are specific to the search implementation.
Search any field by typing the field name, followed by a colon, and then the term you are looking for. For example, to find logs with a message that contains "called the function Value Selector" in the app "my-app", enter either of the following:
  * `application: "my-app" AND message: "called the function Value Selector"`
  * `application: "my-app" AND "called the function Value Selector"`


The default field, `message`, does not require a field indicator in the query. However, the `application` field must be specified before the `message` field in this query.