Skip to content

Commit 540b7e8

Browse files
DataUI VCS Robotdtikhonova
DataUI VCS Robot
authored and
dtikhonova
committed
Release 24.02.2025
* Billing: documented how to change payment method from bank transfer to a card. * Cloud Desktop: added price examples. * Foundation Models: added information on new YandexGPT Pro release. * Foundation Models: structured output documented. * Serverless Integrations: added tutorial on how to configure Yandex Workflow workflow which using Yandex Tracker, YandexGPT API and Yandex Cloud Postbox integrations. * Fixes and improvements.
1 parent 887d557 commit 540b7e8

File tree

89 files changed

+1755
-874
lines changed

Some content is hidden

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

89 files changed

+1755
-874
lines changed

‎en/_includes/managed-kubernetes/alb-ref/gateway.md

-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# Gateway resource fields
22

3-
43
The `Gateway` resource defines the rules for accepting and routing ([HTTPRoute](../../../application-load-balancer/k8s-ref/http-route.md) and [TLSRoute](../../../application-load-balancer/k8s-ref/tls-route.md) resources) incoming traffic. [{{ alb-name }} Gateway API](../../../application-load-balancer/tools/k8s-gateway-api/index.md) uses these rules to create:
54

65
* [Load balancer](../../../application-load-balancer/concepts/application-load-balancer.md) with the required listeners.

‎en/_includes/managed-kubernetes/alb-ref/grpc-backend-group.md

-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# GrpcBackendGroup resource fields
22

3-
43
`GrpcBackendGroup` enables you to combine backends that are {{ k8s }} services and that gRPC traffic is distributed to, into a group. The [{{ alb-name }} Ingress controller](../../../application-load-balancer/tools/k8s-ingress-controller/index.md) uses these resources to create [backend groups](../../../application-load-balancer/concepts/backend-group.md).
54

65
You need to add a reference to `GrpcBackendGroup` to the [`Ingress`](../../../application-load-balancer/k8s-ref/ingress.md) resource. This `Ingress` must have the `ingress.alb.yc.io/protocol: grpc` annotation.

‎en/_includes/managed-kubernetes/alb-ref/http-backend-group.md

-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# `HttpBackendGroup` resource fields
22

3-
43
`HttpBackendGroup` enables you to combine backends that are {{ k8s }} services and that traffic is distributed to, into a group. The [{{ alb-name }} Ingress controller](../../../application-load-balancer/tools/k8s-ingress-controller/index.md)uses these resources to create [backend groups](../../../application-load-balancer/concepts/backend-group.md).
54

65
You need to add a reference to `HttpBackendGroup` to the [`Ingress` resource](../../../application-load-balancer/k8s-ref/ingress.md).

‎en/_includes/managed-kubernetes/alb-ref/http-route.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# HTTPRoute resource fields
22

3-
4-
53
The `HTTPRoute` resource defines the rules for routing traffic to backends that are {{ k8s }} services ([Service](../../../application-load-balancer/k8s-ref/service-for-gateway.md) resources) or for redirecting traffic. `HTTPRoute` receives incoming traffic from the [`Gateway` resources](../../../application-load-balancer/k8s-ref/gateway.md) whose requirements it meets.
64

75
`HTTPRoute` is designed for application developers. Cluster operators should use `Gateway`.

‎en/_includes/managed-kubernetes/alb-ref/ingress.md

-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# Ingress resource fields and annotations
22

3-
43
The `Ingress` resource defines the rules for distribution of incoming traffic between {{ k8s }} services. The [{{ alb-name }} Ingress controller](../../../application-load-balancer/tools/k8s-ingress-controller/index.md) uses these rules to create a [load balancer](../../../application-load-balancer/concepts/application-load-balancer.md) with the requisite listeners and [HTTP routers](../../../application-load-balancer/concepts/http-router.md). The [services](../../../application-load-balancer/k8s-ref/service-for-ingress.md) acting as {{ alb-name }} backends may be specified in `Ingress` directly or as part of [`HttpBackendGroup` backend groups](../../../application-load-balancer/k8s-ref/http-backend-group.md).
54

65
`Ingress` is a standard {{ k8s }} resource. Below, you can find the descriptions of the resource fields and annotations the {{ alb-name }} Ingress controller interfaces with. For a full description of the resource configuration, see the [{{ k8s }} documentation](https://kubernetes.io/docs/reference/kubernetes-api/service-resources/ingress-v1/).

‎en/_includes/managed-kubernetes/alb-ref/service-for-gateway.md

-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# Fields and annotations of the Service resource for the Gateway API
22

3-
43
The `Service` resource represents the [{{ k8s }} service](../../../managed-kubernetes/concepts/index.md#service). For the [Gateway API](../../../application-load-balancer/tools/k8s-gateway-api/index.md), services are backends between which the incoming traffic is distributed within a {{ managed-k8s-name }} cluster. Services representing {{ alb-name }} backends are specified in the [HTTPRoute](../../../managed-kubernetes/alb-ref/http-route.md) resource.
54

65
`Service` is a standard {{ k8s }} resource. Below, you can find the descriptions of the resource fields and annotations the {{ alb-name }} tools for {{ managed-k8s-name }} interface with. For a full description of the resource configuration, see the [{{ k8s }} documentation](https://kubernetes.io/docs/reference/kubernetes-api/service-resources/service-v1/).

‎en/_includes/managed-kubernetes/alb-ref/service-for-ingress.md

-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# Fields and annotations of the Service resource for the Ingress controller
22

3-
43
The `Service` resource represents the [{{ k8s }} service](../../../managed-kubernetes/concepts/index.md#service). For the [Ingress controller](../../../application-load-balancer/tools/k8s-ingress-controller/index.md), {{ alb-name }} services are backends between which the incoming traffic is distributed within a {{ managed-k8s-name }} cluster. Services representing {{ alb-name }} backends may be specified in the [Ingress](../../../managed-kubernetes/alb-ref/ingress.md) resource either directly or as part of [HttpBackendGroup](../../../managed-kubernetes/alb-ref/http-backend-group.md) backend groups.
54

65
`Service` is a standard {{ k8s }} resource. Below, you can find the descriptions of the resource fields and annotations the {{ alb-name }} tools for {{ managed-k8s-name }} interface with. For a full description of the resource configuration, see the [{{ k8s }} documentation](https://kubernetes.io/docs/reference/kubernetes-api/service-resources/service-v1/).

‎en/_includes/managed-kubernetes/alb-ref/tls-route.md

-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# TLSRoute resource fields
22

3-
43
The `TLSRoute` resource sets the rules for routing traffic between {{ k8s }} service type backends ([Service](../../../application-load-balancer/k8s-ref/service-for-gateway.md) resources). `TLSRoute` receives incoming traffic from the [Gateway](../../../application-load-balancer/k8s-ref/gateway.md) resources whose requirements it satisfies.
54

65
`TLSRoute` is designed for application developers. Cluster operators should use `Gateway`.

‎en/_includes/managed-kubernetes/alb-ref/upgrade-alb-ingress-controller.md

-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# Updating an {{ alb-name }} Ingress controller for {{ managed-k8s-name }}
22

3-
43
[ALB Ingress Controller](/marketplace/products/yc/alb-ingress-controller) versions 0.2.0 and later are not compatible with versions 0.1.x. This causes limitations associated with [backend groups](../../../application-load-balancer/tools/k8s-ingress-controller/principles.md).
54

65
One of the ways to create a backend group is to specify [rules](../../../application-load-balancer/k8s-ref/ingress.md#rule) in the `Ingress` resource. In ALB Ingress Controller versions prior to 0.2.0, each backend group corresponds to a bundle of `host`, `http.paths.path`, and `http.paths.pathType` parameters. In versions 0.2.0 and later, the backend group corresponds to the `backend.service` parameter in the `Ingress` resource. This parameter specifies [{{ k8s }}](../../../managed-kubernetes/concepts/service.md). For more information about parameter values and the `Ingress` resource configuration, see the [{{ k8s }} documentation](https://kubernetes.io/docs/concepts/services-networking/ingress/).

‎en/_pricing_examples/cloud-desktop/usd.md

+45
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
Calculating the cost of computing resources:
2+
3+
> ($0.00664 × 2 + $0.00344 × 2) × 1,000 = {% calc [currency=USD] (0,00664 × 2 + 0,00344 × 2) × 1000 %}
4+
>
5+
> {% calc [currency=USD] (0,00664 × 2 + 0,00344 × 2) × 1000 %}: Total cost of 1,000 hours of computing resource operation.
6+
7+
Where:
8+
* $0.00664: Cost of using 50% vCPU per hour.
9+
* 2: Number of vCPUs.
10+
* $0.00344: Cost of using 1 GB of RAM per hour.
11+
* 2: Amount of RAM (GB).
12+
* 1,000: Total operating time of all desktops in the group over the month.
13+
14+
Cost calculation for boot disks:
15+
16+
> {% calc [currency=USD] 0,000176 × 720 %} × 50 × 10 = {% calc [currency=USD] 0,000176 × 720 × 50 × 10 %}
17+
>
18+
> {% calc [currency=USD] 0,000176 × 720 × 50 × 10 %}: Total cost of boot disk operation.
19+
20+
Where:
21+
* {% calc [currency=USD] 0,000176 × 720 %}: Cost of using 1 GB of an SSD boot disk per month.
22+
* 50: Boot disk size (GB).
23+
* 10: Number of desktops in the group.
24+
25+
Cost calculation for working disks:
26+
27+
> {% calc [currency=USD] 0,000048 × 720 %} × 30 × 10 = {% calc [currency=USD] 0,000048 × 720 × 30 × 10 %}
28+
>
29+
> {% calc [currency=USD] 0,000048 × 720 × 30 × 10 %}: Total cost of working disk operation.
30+
31+
Where:
32+
* {% calc [currency=USD] 0,000048 × 720 %}: Cost of using 1 GB of an HDD working disk per month.
33+
* 30: Working disk size (GB).
34+
* 10: Number of desktops in the group.
35+
36+
Total cost calculation:
37+
38+
> {% calc [currency=USD] (0,00664 × 2 + 0,00344 × 2) × 1000 %} + {% calc [currency=USD] 0,000176 × 720 × 50 × 10 %} + {% calc [currency=USD] 0,000048 × 720 × 30 × 10 %} = {% calc [currency=USD] ((0,00664 × 2 + 0,00344 × 2) × 1000) + (0,000176 × 720 × 50 × 10) + (0,000048 × 720 × 30 × 10) %}
39+
>
40+
> {% calc [currency=USD] ((0,00664 × 2 + 0,00344 × 2) × 1000) + (0,000176 × 720 × 50 × 10) + (0,000048 × 720 × 30 × 10) %}: Total cost of using {{ cloud-desktop-name }} per month.
41+
42+
Where:
43+
* {% calc [currency=USD] (0,00664 × 2 + 0,00344 × 2) × 1000 %}: Cost of computing resources.
44+
* {% calc [currency=USD] 0,000176 × 720 × 50 × 10 %}: Cost of boot disks.
45+
* {% calc [currency=USD] 0,000048 × 720 × 30 × 10 %}: Cost of working disks.

‎en/application-load-balancer/operations/k8s-gateway-api-install.md

-1
Original file line numberDiff line numberDiff line change
@@ -5,5 +5,4 @@ description: Follow this guide to install the {{ alb-name }} Gateway API for {{
55

66
# Installing {{ alb-name }} Gateway API for {{ managed-k8s-name }}
77

8-
98
{% include notitle [gateway-api-install](../../_includes/managed-kubernetes/gateway-api-install.md) %}

‎en/application-load-balancer/operations/k8s-ingress-controller-apply.md

-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ description: Follow this guide to create or update {{ alb-name }} resources base
55

66
# Creating or updating {{ alb-name }} resources based on {{ managed-k8s-name }} configuration
77

8-
98
To manage {{ alb-name }} resources using an [Ingress controller](../tools/k8s-ingress-controller/index.md) and [Gateway API](../tools/k8s-gateway-api/index.md) for {{ managed-k8s-full-name }}, create a configuration consisting of YAML files with descriptions of {{ k8s }} resources: `Ingress`, `HttpBackendGroup`, `Gateway`, `HTTPRoute`, etc.
109

1110
## Getting started {#prerequisites}

‎en/application-load-balancer/tools/index.md

-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ description: In this tutorial, you will learn about the {{ alb-name }} tools for
55

66
# Tools for {{ managed-k8s-name }}
77

8-
98
{{ alb-name }} provides the following tools to create load balancers and manage them in {{ managed-k8s-name }} clusters:
109

1110
* {{ alb-name }} [Ingress controller](k8s-ingress-controller/index.md): For `Ingress` resources.

‎en/application-load-balancer/tools/k8s-gateway-api/index.md

-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ description: '{{ alb-name }} provides the Gateway API as a tool to create and ma
55

66
# Gateway API for {{ managed-k8s-name }}
77

8-
98
{{ alb-name }} provides the Gateway API as a tool to create and manage load balancers in [{{ managed-k8s-full-name }} clusters](../../../managed-kubernetes/concepts/index.md#kubernetes-cluster). For more information about the Gateway API project, visit its [website](https://gateway-api.sigs.k8s.io/).
109

1110
Once you install the Gateway API, you can use it to create a resource named `Gateway` and associated `HTTPRoute` resources:

‎en/application-load-balancer/tools/k8s-ingress-controller/index.md

-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ description: '{{ alb-name }} provides the Ingress controller, a tool for creatin
55

66
# Ingress controller for {{ managed-k8s-name }}
77

8-
98
{{ alb-name }} provides the {{ alb-name }} Ingress controller — a tool you can use to create and manage load balancers in [{{ managed-k8s-full-name }} clusters](../../../managed-kubernetes/concepts/index.md#kubernetes-cluster).
109

1110
The Ingress controller installed in the cluster will automatically deploy [L7 load balancers](../../concepts/application-load-balancer.md) with all the required {{ alb-name }} resources based on the configuration of the [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) resources you created.

‎en/application-load-balancer/tools/k8s-ingress-controller/principles.md

-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ description: Learn about the {{ alb-name }} Ingress controller and the relations
55

66
# How the {{ alb-name }} Ingress controller works
77

8-
98
An [{{ alb-name }} Ingress controller for {{ managed-k8s-name }}](index.md) has two [pods](../../../managed-kubernetes/concepts/index.md#pod):
109

1110
* The primary `yc-alb-ingress-controller-*` pod responsible for creating and updating {{ alb-name }} resources. You can use its logs to follow the operations with the resources.

‎en/application-load-balancer/tools/k8s-ingress-controller/security-groups.md

-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ description: For the Ingress controller or Gateway API to work properly, you nee
55

66
# Configuring security groups for {{ alb-name }} tools for {{ managed-k8s-name }}
77

8-
98
For the [Ingress controller](index.md) or [Gateway API](../k8s-gateway-api/index.md) to work properly, you need to configure [security groups](../../../vpc/concepts/security-groups.md) for your [cluster](../../../managed-kubernetes/concepts/index.md#kubernetes-cluster), [{{ managed-k8s-full-name }} node groups](../../../managed-kubernetes/concepts/index.md#node-group), and {{ alb-name }} [load balancer](../../concepts/application-load-balancer.md).
109

1110
You can use different security groups (recommended) or the same group for the cluster, the node groups, and the load balancer.

‎en/application-load-balancer/tools/k8s-ingress-controller/service-account.md

-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ description: In this tutorial, you will learn which roles a service account requ
55

66
# Service account for {{ alb-name }} tools for {{ managed-k8s-name }}
77

8-
98
The {{ alb-name }} tools for {{ managed-k8s-name }}, i.e., [Ingress controller](index.md) and [Gateway API](../k8s-gateway-api/index.md), deploy the infrastructure on behalf of a [service account](../../../iam/concepts/users/service-accounts.md). This account requires the following permissions:
109

1110
{% list tabs %}

‎en/cloud-desktop/pricing.md

+17-2
Original file line numberDiff line numberDiff line change
@@ -27,15 +27,15 @@ The {{ cloud-desktop-name }} usage cost is based on:
2727

2828
The monthly prices are based on 720 hours per month.
2929

30-
### Computing resources usage {#use-resources}
30+
### Using computing resources {#use-resources}
3131

3232
The cost of a desktop depends on the allocated computing resources and usage time. Attached disks and network usage are charged separately.
3333

3434
The cost is calculated for the time of using the desktop, when the status switches to `CREATING` (during creation) or `STARTING` (during startup) until it is completely stopped. The time when the desktop is stopped is not charged.
3535

3636
The desktop starts automatically once it is created.
3737

38-
### Storage usage {#use-storage}
38+
### Using disks {#use-storage}
3939

4040
Disks are charged for whether desktops are running or not.
4141

@@ -60,3 +60,18 @@ Disks are charged for whether desktops are running or not.
6060
{% endlist %}
6161

6262
{% include [egress-traffic-pricing](../_includes/egress-traffic-pricing.md) %}
63+
64+
## Cost calculation example {#price-example}
65+
66+
Here is an example of calculating the cost of using {{ cloud-desktop-name }} for one month, for a group of 10 desktops with the following configuration:
67+
68+
* Computing resources: 2 x 50% vCPUs and 2 GB of RAM.
69+
* Boot disk: 50 GB SSD.
70+
* Working disk: 30 GB HDD.
71+
* Total operating time of all desktops over the month: 1,000 hours.
72+
73+
74+
75+
{% include [usd-cloud-desktop](../_pricing_examples/cloud-desktop/usd.md) %}
76+
77+

‎en/compute/operations/vm-connect/ssh.md

-4
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
title: How to connect to a Linux VM via SSH
3-
description: 'Follow this guide to connect to a VM using an SSH key pair: the public key resides on the VM, and the private one is kept by the user.'
4-
---
51

62
# Connecting to a Linux VM via SSH
73

‎en/compute/operations/vm-create/create-from-user-image.md

+4
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,7 @@
1+
---
2+
title: How to create a VM from a custom image
3+
description: Follow this guide to create a VM from a custom image.
4+
---
15

26
# Creating a VM from a custom image
37

‎en/presets.yaml

+3
Original file line numberDiff line numberDiff line change
@@ -8272,6 +8272,7 @@ default:
82728272
button_validate: Verify address
82738273
label_address: Domain
82748274
label_configuration-sets: Configurations
8275+
label_dns-record-name: Name
82758276
label_dns-record-value: Value
82768277
label_event-destinations: Subscriptions
82778278
label_identities: Addresses
@@ -8554,8 +8555,10 @@ default:
85548555
button_create-workflow: Create workflow
85558556
label_additional-parameters: Additional parameters
85568557
label_input_data: Input data
8558+
label_run-workflow: Execute
85578559
label_service: Workflows
85588560
label_service-account: Service account
8561+
label_timeline: Timeline
85598562
label_workflow-executions: Executions
85608563
spec-editor-type_label_text-editor: YaML specification
85618564
smart-web-security:

‎en/speechkit/stt-v3/api-ref/AsyncRecognizer/deleteRecognition.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ sourcePath: en/_api-ref/ai/stt/v3/stt-v3/api-ref/AsyncRecognizer/deleteRecogniti
88
## HTTP request
99

1010
```
11-
DELETE https://stt.{{ api-host }}/stt/v3/deleteRecognition
11+
DELETE https://{{ api-host-sk-stt }}/stt/v3/deleteRecognition
1212
```
1313

1414
## Query parameters {#speechkit.stt.v3.DeleteRecognitionRequest}

‎en/speechkit/stt-v3/api-ref/AsyncRecognizer/getRecognition.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ sourcePath: en/_api-ref/ai/stt/v3/stt-v3/api-ref/AsyncRecognizer/getRecognition.
88
## HTTP request
99

1010
```
11-
GET https://stt.{{ api-host }}/stt/v3/getRecognition
11+
GET https://{{ api-host-sk-stt }}/stt/v3/getRecognition
1212
```
1313

1414
## Query parameters {#speechkit.stt.v3.GetRecognitionRequest}

‎en/speechkit/stt-v3/api-ref/AsyncRecognizer/recognizeFile.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ sourcePath: en/_api-ref/ai/stt/v3/stt-v3/api-ref/AsyncRecognizer/recognizeFile.m
88
## HTTP request
99

1010
```
11-
POST https://stt.{{ api-host }}/stt/v3/recognizeFileAsync
11+
POST https://{{ api-host-sk-stt }}/stt/v3/recognizeFileAsync
1212
```
1313

1414
## Body parameters {#speechkit.stt.v3.RecognizeFileRequest}

‎en/speechkit/tts-v3/api-ref/Synthesizer/utteranceSynthesis.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Synthesizing text into speech.
1010
## HTTP request
1111

1212
```
13-
POST https://tts.{{ api-host }}/tts/v3/utteranceSynthesis
13+
POST https://{{ api-host-sk-tts }}/tts/v3/utteranceSynthesis
1414
```
1515

1616
## Body parameters {#speechkit.tts.v3.UtteranceSynthesisRequest}

‎en/speechkit/tts-v3/api-ref/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The SpeechKit Text To Speech API v3 allows application developers to use speech
99

1010
**Interface definitions** available at [GitHub](https://github.com/yandex-cloud/cloudapi/tree/master/yandex/cloud/ai/tts/v3).
1111

12-
**Service URL**: `https://tts.{{ api-host-sk-tts }}`
12+
**Service URL**: `https://{{ api-host-sk-tts }}`
1313

1414
#|
1515
||Service | Description ||

‎ru/_assets/console-icons/circle-check.svg

+3
Loading

‎ru/_assets/console-icons/timeline.svg

+3
Loading

‎ru/_includes/audit-trails/dp-events-service-list.md

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
* [{{ certificate-manager-full-name }}](../../audit-trails/concepts/events-data-plane.md#certificate-manager)
2+
* [{{ dns-full-name }}](../../audit-trails/concepts/events-data-plane.md#dns)
3+
* [{{ compute-full-name }}](../../audit-trails/concepts/events-data-plane.md#compute)
4+
* [{{ iam-full-name }}](../../audit-trails/concepts/events-data-plane.md#iam)
5+
* [{{ kms-full-name }}](../../audit-trails/concepts/events-data-plane.md#kms)
6+
* [{{ lockbox-full-name }}](../../audit-trails/concepts/events-data-plane.md#lockbox)
7+
* [{{ mch-full-name }}](../../audit-trails/concepts/events-data-plane.md#mch)
8+
* [{{ managed-k8s-full-name }}](../../audit-trails/concepts/events-data-plane.md#managed-service-for-kubernetes)
9+
* [{{ mmg-full-name }}](../../audit-trails/concepts/events-data-plane.md#mmg)
10+
* [{{ mmy-full-name }}](../../audit-trails/concepts/events-data-plane.md#mmy)
11+
* [{{ mpg-full-name }}](../../audit-trails/concepts/events-data-plane.md#mpg)
12+
* [{{ mrd-full-name }}](../../audit-trails/concepts/events-data-plane.md#mrd)
13+
* [{{ objstorage-full-name }}](../../audit-trails/concepts/events-data-plane.md#objstorage)
14+
* [{{ sd-full-name }}](../../audit-trails/concepts/events-data-plane.md#security-deck)
15+
* [{{ speechsense-full-name }}](../../audit-trails/concepts/events-data-plane.md#speechsense)
16+
* [{{ sws-full-name }}](../../audit-trails/concepts/events-data-plane.md#sws)
17+
* [{{ wiki-full-name }}](../../audit-trails/concepts/events-data-plane.md#wiki)
18+
* [{{ websql-full-name }}](../../audit-trails/concepts/events-data-plane.md#websql)

0 commit comments

Comments
 (0)