# Search Query Language

The Search syntax is very close to the Lucene syntax. By default, all message fields are included in the same search if you don't specify a message field to search in.

## Syntax Support

* Messages that include the term `ssh`
* Messages that include the term `ssh` or `login`
* Messages that include the exact phrase `ssh` `login`
* Messages where the field `type` include `ssh`
* Messages where the field `type` includes `ssh` or `login`
* Messages where the field `type` includes the exact phrase `ssh` `login`
* Messages that have the field type
* Messages that do not have the field type
* Messages that match the regular expression `ethernet[0-9]+`
* By default, all terms or phrases OR connected so all messages that have at least one hit are returned. You can use Boolean operators and groups&#x20;

## Escaping

The following character must be escaped with a backslash:

```
& | : \ / + - ! ( ) { } [ ] ^ " ~ * ?
```

Example:

```
resource:\/posts\/45326
```

## Error Types

When entering your queries be sure to look out for warnings and exceptions. If you enter a query leona won't understand, an icon with a yellow exclamation mark appears along with a message with the warnings or exceptions. They include:

* Parse exception
* Invalid operator
* Unknown field
* Parameter error


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ciusji.gitbook.io/leona/searching/search-query-language.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
