> For the complete documentation index, see [llms.txt](https://digitalgarden.batamladen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digitalgarden.batamladen.com/notes/query-languages/kql/syntax-and-query-structure.md).

# Syntax and Query Structure

### Some important rules:

1. You can put as many spaces you want btw the pipe and the command

```kql
cluster('help').database('SecurityLogs').Email
|     where subject == "jasade"
```

2. You can put many pipe commands in one line

```kql
cluster('help').database('SecurityLogs').Email
| where subject == "jasade" | sort by event_time asc
```

3. Double slash to comment '//'

```kql
//this is a comment
cluster('help').database('SecurityLogs').Email
| where subject == "jasade" | sort by event_time asc
```

4. KQL is mostly case-sensitive
5. No quotes around field names

### Comparison operators

* `==` equals to

* `!=` not equal to

```
Table
| where FIrstName != "peter" //all people not named peter are returned
```

* \=\~ not case sensitive

```kql
Table
| where FIrstName =~ "peter" //all uppercase, lowercase, combined is returned
```

### Query order

How you filter your data matters!

If you filter first for the random 10 rows with 'take 10' and after that you search for all the users named 'peter' you wont get the same result as if you first searched for the name peter and than took random 10 rows.


---

# 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://digitalgarden.batamladen.com/notes/query-languages/kql/syntax-and-query-structure.md?ask=<question>&goal=<user_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.