Query Input
The Query Input uses FlyQL syntax. The canonical reference (operators, value forms, lists, dates, pattern matching, transformers, renderers) lives at docs.flyql.dev — this page only covers what is specific to Telescope.
How Telescope evaluates queries
Section titled “How Telescope evaluates queries”Each source kind compiles or evaluates the same FlyQL query differently:
| Source kind | Evaluation path |
|---|---|
| ClickHouse | Compiled to a SQL WHERE clause via the FlyQL ClickHouse generator. |
| StarRocks | Compiled to a SQL WHERE clause via the FlyQL StarRocks generator. |
| Docker | Logs are pulled from the daemon and matched in-process by the FlyQL Python matcher. |
| Kubernetes | Logs are pulled from the Kubernetes API and matched in-process by the same matcher. |
For SQL-backed sources, supported operators ultimately depend on what the dialect can express. For Docker/Kubernetes, all evaluation happens in Python and behaves as documented in the FlyQL syntax reference.
like and pattern matching
Section titled “like and pattern matching”like and the regex operators (~, !~) are supported across all sources, but the semantics differ slightly:
- ClickHouse / StarRocks:
likecompiles to native SQLLIKE(%,_wildcards). Regex compiles tomatch()/ equivalent. - Docker / Kubernetes: evaluated by google-re2 on the server. Use regex for wildcard matching:
pod ~ "^api-.*"instead ofpod like "api-*".
Editor features
Section titled “Editor features”The query editor (powered by flyql-vue) provides:
- Inline diagnostics: parse errors and unknown columns are flagged with red squiggles and explained in a panel under the editor.
- Context-aware suggestions: column names, operators, values, transformers, and boolean operators are suggested based on cursor position.
Tabcycles between value and column suggestions when typing a value. - Value autocomplete: for columns with
autocomplete: truein the source schema, value suggestions are fetched from the underlying datastore (ClickHouseDISTINCT/ StarRocksGROUP BY). - JSON key discovery: typing
column.on a JSON-typed column triggers a server lookup that suggests nested keys actually present in your recent data, including for ClickHouseJSON/JSONStringcolumns and Kuberneteslabels/annotations. - Submit:
Ctrl+Enter(orCmd+Enter) executes the query.
Examples
Section titled “Examples”host = localhosthost != localhost and message ~ "^2025-"(host = localhost or host = remote) and not host = puppetstatus in [200, 201, 204]labels.'app.kubernetes.io/component' = "controller"active and not archivedFor deeper coverage — operators (has, in, truthy checks, ranges), date literals, parameters, reserved words, and the transformer/renderer pipeline — see the FlyQL syntax docs.