Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

YDBDOCS-740: mention column-oriented tables in the Grafana article #8705

Merged
merged 2 commits into from
Sep 9, 2024
Merged

YDBDOCS-740: mention column-oriented tables in the Grafana article #8705

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7d50e97
YDBDOCS-740: mention column-oriented tables in the Grafana article
blinkov Sep 4, 2024
a9bb4f8
Update grafana.md
blinkov Sep 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion ydb/docs/en/core/integrations/grafana.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,11 +98,16 @@ GROUP BY `responseStatus`, `timestamp`
ORDER BY `timestamp`
```

{% note tip %}

For this kind of queries, using [column-oriented tables](../concepts/datamodel/table.md#column-oriented-tables) will likely be beneficial in terms of performance.

{% endnote %}

### Tables { #tables }

Table visualizations will always be available for any valid {{ ydb-short-name }} query that returns exactly one result set.


![Table](../_assets/grafana/table.png)

### Visualizing logs with the Logs Panel
Expand Down
7 changes: 7 additions & 0 deletions ydb/docs/ru/core/integrations/grafana.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,7 @@ datasources:
#### Многострочные временные ряды

Чтобы создать многострочный временной ряд, результаты запроса должны содержать в себе как минимум три поля:

* поле с типом данных `Date`, `Datetime` или `Timestamp` (на текущий момент поддержана работа со временем только во временной зоне UTC)
* метрика - поле с типом `Int64`, `Int32`, `Int16`, `Int8`, `Uint64`, `Uint32`, `Uint16`, `Uint8`, `Double` или `Float`
* либо метрика, либо поле с типом `String` или `Utf8` - значение для разбиения метрик по отдельным рядам.
Expand All @@ -99,6 +100,12 @@ GROUP BY `responseStatus`, `timestamp`
ORDER BY `timestamp`
```

{% note tip %}

Для таких запросов использование [колоночных таблиц](../concepts/datamodel/table.md#column-oriented-tables) может быть полезным с точки зрения производительности.

{% endnote %}

### Таблицы { #tables }

Табличное представление доступно для любого валидного {{ ydb-short-name }} запроса, возвращающего ровно один набор результатов.
Expand Down
Loading