# Keyword Searches

## CLQL Keyword Searches

Use **keyword searches** to filter log messages by specific metadata fields rather than searching all field values. Keyword fields are prefixed with `_`.

> **Tip:** Start typing `_` in the search box for autocomplete suggestions of available metadata fields.

Below are some supported keyword fields with examples:

### `_createdAt`

Filter by message timestamp.

```graphql
_createdAt >= 2024-12-13T14:00:21.185Z
_createdAt > 2024-12-13T14:00 _createdAt < 2024-12-13T15:00
```

### `_logId`

Filter by log ID.

```graphql
_logId = oVn9Pa9DzJuWtAA71sSz3y
```

### `_name`

Filter by name.

```graphql
_name = started
_name != finished
_name = get*details
_name = "Get User Details"
```

### `_logType`

Filter by log type.

```graphql
_logType = log-tap
```

### `_message`

Filter by message content.

```graphql
_message = foo@bar.baz
_message = https://*
_message = 2024-12-16T14:*
_message = 10.224.0.*
```

### `_level`

Filter by level.

```graphql
_level != info
_level in (warn, error)
_level in ["warn", "error"]
_level = error
```

### `_type`

Filter by message type.

```graphql
_type = json
```

### `_source`

Filter by source.

```graphql
_source = agent
```

### `_sessionId`

Filter by session ID.

```graphql
_sessionId = uoqtfXVzCAAgLLjw9gswnx
```

### `_correlationId`

Filter by correlation ID.

```graphql
_correlationId = qSq2ZW49Hq3RQFbuvWDzvS
```

### `_kind`

Filter by kind.

```graphql
_kind = execution
```

### `_subKind`

Filter by sub kind.

```graphql
_subKind = admin-api-agent*
```

### `_typeId`

Filter by type ID.

```graphql
_typeId = flow
```

### `_instance`

Filter by instance.

```graphql
_instance = http-api*
```


---

# 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://docs.contextual.io/documentation-and-resources/tenants/tenant-logs/contextual-log-query-language-clql/keyword-searches.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.