Kusto Query Language (KQL). Use this tag with any questions or advice of operator, complicated query, performance challenges or missing capabilities. KQL is a read-only request to process data and return results. The request is stated in plain text, using a data-flow model designed to make the syntax easy, author and automate. The query uses schema entities that are organized in a hierarchy similar to SQL's: databases, tables, and columns.
Pluralsight Course: Basics of KQL
How to write a good KQL question?
- Provide proper sample data.
- That includes data + schema (tables' names + columns' names & data types).
- Make sure you cover all relevant edge cases.
- No need to post real data. Synthetic data is good enough, as long as it matches the structure and patterns of the original data.
- Provide required results.
- Required results should match the provided sample data.
- Provide _short_ explanation.
- Adding code / pseudo code is fine, as long as you narrow it to the minimal form needed to make your point.
- DO NOT post your 100 rows query As Is
- The code should match the sample data schema.
Per StackOverflow guidelines, DO NOT post images of code or data.
- Keep your code formatted by wrapping it with triple-backtick (```), e.g.:
```
MyTable
| count
```
- For sample data it is recommended to use datatable
- For required results you can use datatable or textual format. You can use online tool such as https://ozh.github.io/ascii-tables/, to transform your data, preferably with output type of Github Markdown, e.g.:
Original data
a y z
1 2 3
4 5 6
GitHub Markdown
| a | y | z |
|---|---|---|
| 1 | 2 | 3 |
| 4 | 5 | 6 |
How it looks on your post:
| a | y | z |
|---|---|---|
| 1 | 2 | 3 |
| 4 | 5 | 6 |
