Skip to content

Commit acee199

Browse files
author
DataUI VCS Robot
committed
Release 14.01.2022
* Audit Trails: added solution for using Yandex Cloud Logging and Yandex Cloud Functions. * Data Transfer: added a warning to whitelist IPs used by the service. * Managed Service for Kubernetes: added information about network in Managed Service for Kubernetes. * Translations updated. * Fixes and improvements.
1 parent 78e1914 commit acee199

File tree

249 files changed

+3863
-1122
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

249 files changed

+3863
-1122
lines changed
Binary file not shown.
Loading
Loading
6.3 KB
Loading
Loading
Loading
Loading
Loading
6.33 KB
Loading
Loading
14.8 KB
Loading
Loading
Loading
Loading
Loading

en/_assets/datasphere/disk.svg

Lines changed: 88 additions & 0 deletions
Loading

en/_assets/dns/security/service-roles-hierarchy.svg

Lines changed: 4 additions & 17 deletions
Loading
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
1. Go to the [connections page](https://datalens.yandex.com/connections).
2+
1. Click **Create connection**.
3+
1. Select the **ClickHouse** connection.
4+
5+
1. In the window that opens, specify the connection parameters:
6+
7+
* Connection name: `Sample ClickHouse`.
8+
* Connection type: **Specify manually**.
9+
* Host name: `rc1a-ckg8nrosr2lim5iz.mdb.yandexcloud.net`.
10+
* HTTP interface port: `8443` (default).
11+
* Username: `samples_ro`.
12+
* Password: `MsgfcjEhJk`.
13+
14+
1. Enable the **HTTPS** option and **Allow subqueries in datasets and queries from charts**.
15+
1. Check the connection and click **Create**.
16+
17+
![create-connection](../../../_assets/datalens/sql-chart/create-sample-connection-sql-chart.png)
18+
19+
Wait for the connection to be saved.
20+
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
`dns.admin`: enables you to view, create, edit, and delete [DNS zones](../../../dns/concepts/dns-zone.md) and [resource records](../../../dns/concepts/resource-record.md) as well as control DNS zone access.

en/_includes/iam/roles/dns-admin.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
### dns.admin {#dns-admin}
2+
3+
The `dns.admin` role includes the following privileges:
4+
5+
* Viewing, creating, editing, and deleting [DNS zones](../../../dns/concepts/dns-zone.md) and [resource records](../../../dns/concepts/resource-record.md).
6+
* Managing access to DNS zones.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
`dns.editor`: enables you to view, create, edit, and delete [DNS zones](../../../dns/concepts/dns-zone.md) and [resource records](../../../dns/concepts/resource-record.md).

en/_includes/iam/roles/dns-editor.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
### dns.editor {#dns-editor}
2+
3+
The `dns.editor` role includes permissions to view, create, edit, and delete [DNS zones](../../../dns/concepts/dns-zone.md) and [resource records](../../../dns/concepts/resource-record.md).
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
`dns.viewer`: enables you to view [DNS zones](../../../dns/concepts/dns-zone.md) and [resource records](../../../dns/concepts/resource-record.md).

en/_includes/iam/roles/dns-viewer.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
### dns.viewer {#dns-viewer}
2+
3+
The `dns.viewer` role enables you to view [DNS zones](../../../dns/concepts/dns-zone.md) and [resource records](../../../dns/concepts/resource-record.md).
Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,4 @@
11
The disk size is specified in bytes by default. You can specify a different unit of measurement using the applicable suffix.
22

3-
| Name | Example of a YAML file entry: |
4-
| ----- | ----- |
5-
| Kilobyte | 1073741824k |
6-
| Megabyte | 1048576m |
7-
| Gigabyte | 1024g |
8-
| Terabyte | 1t |
3+
{% include [yaml-int64-suffixes](yaml-int64-suffixes.md) %}
94

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
| Suffix | Prefix and multiplier | Example |
2+
| ----- | ----- | ----- |
3+
| `k` | kilo- (2^10^) | `640k` = 640 × 2^10^ = `655360` |
4+
| `m` | mega- (2^20^) | `48m` = 48 × 2^20^ = `50331648` |
5+
| `g` | giga- (2^30^) | `10g` = 10 × 2^30^ = `10737418240` |
6+
| `t` | tera- (2^40^) | `4t` = 4 × 2^40^ = `4398046511104` |
7+
| `p` | peta- (2^50^) | `2p` = 2 × 2^50^ = `2251799813685248` |
8+

en/_includes/logging/read-logs.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -72,9 +72,4 @@ You can filter records using the [language of filter expressions](../../logging/
7272
7373
You can view the entries in a log group using the API [read](../../logging/api-ref/grpc/log_reading_service.md) method.
7474
75-
- API
76-
77-
You can view the entries in a log group using the API [read](../../logging/api-ref/grpc/log_reading_service.md) method.
78-
7975
{% endlist %}
80-

en/_includes/mdb/mpg-conn-strings.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -875,3 +875,5 @@ sudo apt update && sudo apt install -y ruby ruby-pg
875875
```bash
876876
ruby connect.rb
877877
```
878+
879+
{% endlist %}

en/_includes/serverless-containers/container-list.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,3 +28,4 @@
2828
+----------------------+--------------------+-----------------------+--------+
2929
```
3030

31+
{% endlist %}
Lines changed: 171 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,171 @@
1+
# Visualizing data with a SQL chart
2+
3+
In this scenario, you will create charts using SQL queries. SQL queries enable you to configure data for visualization in a more flexible way than the standard dataset method does. For example, you can add parameters from dashboards to a SQL query.
4+
5+
We recommend using a SQL chart when creating a conventional chart from a dataset isn't suitable, or when you would like to experiment with data.
6+
7+
A direct connection to a demo database will be used as your data source.
8+
9+
To visualize and analyze data, make sure you have a [ready-to-use cloud](#before-you-begin) and follow these steps:
10+
11+
1. [Create a connection](#create-connection).
12+
1. [Create a SQL chart](#create-sql-chart).
13+
1. [Create a dashboard](#create-dashboard).
14+
1. [Add the SQL chart to the dashboard](#add-sql-chart-to-dashboard).
15+
1. [Add a selector to the dashboard](#add-selector-to-dashboard).
16+
17+
{% note warning %}
18+
19+
* SQL queries only work with databases. CSV, GoogleSheets, Yandex.Metrica, and other service connections do not support SQL queries.
20+
21+
* SQL charts are currently available on non-public dashboards only. If you open a [public dashboard](../../datalens/concepts/datalens-public.md), you will see an error in the chart.
22+
23+
{% endnote %}
24+
25+
## Before you start {#before-you-begin}
26+
27+
{% include [before-you-begin](includes/before-you-begin-datalens.md) %}
28+
29+
## Create a connection {#create-connection}
30+
31+
{% include [datalens-create-sample-connection](../datalens/operations/datalens-create-sample-connection.md) %}
32+
33+
## Create a SQL chart {#create-sql-chart}
34+
35+
1. Go to an existing database connection.
36+
1. Make sure **Raw SQL level****Allow subqueries in datasets and queries from charts** is enabled.
37+
1. In the upper right-hand corner, click **Create SQL chart**.
38+
1. On the **Query** tab, enter the query code:
39+
40+
```sql
41+
SELECT
42+
year(t2.FirstDate) as "Year",
43+
COUNT(t1.ClientID) as "Number of new clients", t3.ClientStatus as "Status"
44+
FROM
45+
samples.MS_SalesFacts t1,
46+
(SELECT
47+
ClientID,
48+
MIN(OrderDatetime) as FirstDate
49+
FROM samples.MS_SalesFacts
50+
GROUP BY ClientID) as t2,
51+
samples.MS_Clients t3
52+
WHERE t1.ClientID =t2.ClientID and t3.ClientID=t2.ClientID and t3.ClientStatus in not_var{{status}} -- status: variable associated with parameter affected by selector
53+
GROUP BY "Year", "Status"
54+
ORDER BY "Year"
55+
```
56+
57+
1. On the **Params** tab, click **Add param** and complete the input fields:
58+
59+
* From the drop-down list, select `string` (default).
60+
* In the **Name** field, enter `status`.
61+
* In the **Default value** field, enter `Базовый`.
62+
* Below, click **Add param value** and enter `Золотой`.
63+
64+
![sql-chart-parameter](../../_assets/datalens/sql-chart/sql-chart-parameter.png)
65+
66+
The added parameter will be associated with the `not_var{{status}}` variable in the query.
67+
68+
{% note info %}
69+
70+
You can control the value of the parameter using a dashboard selector.
71+
72+
{% endnote %}
73+
74+
1. Go back to the **Query** tab. In the lower left-hand corner, click **Run**. Running the query will produce a visualization in the right-hand window.
75+
1. Configure the visualization:
76+
77+
* Select **Column chart** as chart type.
78+
79+
![sql-chart-diagram](../../_assets/datalens/sql-chart/sql-chart-diagram.png)
80+
81+
* Drag the **Year** field to the **X** section.
82+
* Drag the **Number of new clients** field to the **Y** section.
83+
* Drag the **Status** field to the **Colors** section.
84+
* Make sure the **Available** section is empty. This is the section that contains fields not involved in calculations. Otherwise, the visualization will display incorrectly.
85+
86+
![sql-chart-rezult](../../_assets/datalens/sql-chart/sql-chart-rezult.png)
87+
88+
1. In the upper right-hand corner, click **Save**.
89+
90+
You can place the chart created on the dashboard. You can also add a selector to the dashboard to control the SQL chart `status` parameter.
91+
92+
## Create a dashboard {#create-dashboard}
93+
94+
Create a [dashboard](../../datalens/concepts/dashboard.md) to add your charts to.
95+
96+
1. Go to the {{ datalens-short-name }} [home page]({{ link-datalens-main }}).
97+
1. Click **Create dashboard**.
98+
99+
![image](../../_assets/datalens/solution-02/35-create-dashboard.png)
100+
101+
1. Enter `Change in number of clients by year` as the name for the dashboard and click **Create**.
102+
103+
The dashboard created will open for editing.
104+
105+
## Add a SQL chart to your dashboard {#add-sql-chart-to-dashboard}
106+
107+
1. At the top of the page, click **Add** and select **Chart**.
108+
109+
![image](../../_assets/datalens/sql-chart/add-chart.png)
110+
111+
1. In the **Chart** field, click **Select** and select the previously created **New clients** chart from the chart list.
112+
113+
![image](../../_assets/datalens/sql-chart/select-chart.png)
114+
115+
Click **Add**.
116+
117+
1. The chart is displayed on the dashboard. Stretch it to improve visualization.
118+
119+
![image](../../_assets/datalens/sql-chart/add-chart-on-dashboard.png)
120+
121+
1. Save the dashboard.
122+
123+
## Add a selector to the dashboard {#add-selector-to-dashboard}
124+
125+
Add a [selector](../../datalens/concepts/dashboard.md#selector) to be able to filter charts by customer status.
126+
127+
1. At the top of the page, click **Add**.
128+
1. Choose **Selector**.
129+
130+
![image](../../_assets/datalens/sql-chart/add-selector.png)
131+
132+
1. In the **Title** field, enter `Select client status`.
133+
1. Enable the **Show** option.
134+
1. Select **Manual input** as source type.
135+
1. Select **List** as element type.
136+
1. In the **Field name** field, enter `status`. Certain selector values will be passed into this SQL query variable.
137+
1. Click on the **Possible values** input field. In the resulting window, add:
138+
139+
* Золотой
140+
* Серебряный
141+
* Базовый
142+
143+
![image](../../_assets/datalens/sql-chart/add-selector-values.png)
144+
145+
Click **Apply**.
146+
147+
1. Enable **Multiple choice**.
148+
1. In the **Default value** list, specify **Select all**.
149+
150+
![image](../../_assets/datalens/sql-chart/add-selector-select-all.png)
151+
152+
1. Verify the specified selector parameters.
153+
154+
![image](../../_assets/datalens/sql-chart/add-selector-parameters.png)
155+
156+
1. Click **Add**.
157+
1. Place the selector above the chart on the dashboard and stretch to match the width of the chart.
158+
1. Save the dashboard.
159+
160+
![image](../../_assets/datalens/sql-chart/add-selector-on-dashboard.png)
161+
162+
1. Your dashboard is ready. Now, you can filter the chart using the selector.
163+
164+
![image](../../_assets/datalens/sql-chart/selector-2-values.png)
165+
166+
#### See also {#see-also}
167+
168+
- [{#T}](../../datalens/operations/dashboard/add-chart.md)
169+
- [{#T}](../../datalens/operations/dashboard/add-selector.md)
170+
- [SQL charts](../../datalens/concepts/chart/index.md#sql-charts)
171+

en/_includes/tutorials/exchange.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -438,7 +438,7 @@ VMs with Active Directory don't have internet access, so they should be configur
438438
--metadata-from-file user-data=setpass
439439
```
440440
441-
{% list tabs %}
441+
{% endlist %}
442442
443443
1. Connect to `fsw-vm` using RDP.
444444
1. On `fsw-vm`, start the RDP client and use it to connect to `vm-exchange-a`. Enter `Administrator` as the username and then your password. Launch PowerShell.

0 commit comments

Comments
 (0)