Information about existing Yandex StoreDoc clusters
You can request detailed information for each Yandex StoreDoc cluster you have created.
Getting a list of database clusters in your folder
- Open the folder dashboard
. - Navigate to the Yandex StoreDoc service.
If you do not have the Yandex Cloud CLI installed yet, install and initialize it.
By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.
To get a list of Yandex StoreDoc clusters in the default folder, run this command:
yc managed-mongodb cluster list
Result:
+----------------------+------------+-----------------------------+--------+---------+
| ID | NAME | CREATED AT | HEALTH | STATUS |
+----------------------+------------+-----------------------------+--------+---------+
| c9wlk4v14uq7******** | mymg | 2018-11-02T10:04:14.645214Z | ALIVE | RUNNING |
| ... |
+----------------------+------------+-----------------------------+--------+---------+
-
Get an IAM token for API authentication and place it in an environment variable:
export IAM_TOKEN="<IAM_token>" -
Call the Cluster.List method, e.g., via the following cURL
request:curl \ --request GET \ --header "Authorization: Bearer $IAM_TOKEN" \ --url 'https://mdb.api.cloud.yandex.net/managed-mongodb/v1/clusters' \ --url-query folderId=<folder_ID>You can get the folder ID from the list of your cloud folders.
-
Check the server response to make sure your request was successful.
-
Get an IAM token for API authentication and place it in an environment variable:
export IAM_TOKEN="<IAM_token>" -
Clone the cloudapi
repository:cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapiBelow, we assume that the repository contents reside in the
~/cloudapi/directory. -
Call the ClusterService.List method, e.g., via the following gRPCurl
request:grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/mdb/mongodb/v1/cluster_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "folder_id": "<folder_ID>" }' \ mdb.api.cloud.yandex.net:443 \ yandex.cloud.mdb.mongodb.v1.ClusterService.ListYou can get the folder ID from the list of your cloud folders.
-
Check the server response to make sure your request was successful.
Getting cluster details
- Open the folder dashboard
. - Navigate to the Yandex StoreDoc service.
- Click the name of your cluster.
If you do not have the Yandex Cloud CLI installed yet, install and initialize it.
By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.
To get Yandex StoreDoc cluster details, run the following command:
yc managed-mongodb cluster get <cluster_name_or_ID>
You can get the cluster’s name and ID from the list of clusters in your folder.
-
Get an IAM token for API authentication and place it in an environment variable:
export IAM_TOKEN="<IAM_token>" -
Call the Cluster.Get method, e.g., via the following cURL
request:curl \ --request GET \ --header "Authorization: Bearer $IAM_TOKEN" \ --url 'https://mdb.api.cloud.yandex.net/managed-mongodb/v1/clusters/<cluster_ID>'You can get the cluster ID from the list of clusters in your folder.
-
Check the server response to make sure your request was successful.
-
Get an IAM token for API authentication and place it in an environment variable:
export IAM_TOKEN="<IAM_token>" -
Clone the cloudapi
repository:cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapiBelow, we assume that the repository contents reside in the
~/cloudapi/directory. -
Call the ClusterService.Get method, e.g., via the following gRPCurl
request:grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/mdb/mongodb/v1/cluster_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "cluster_id": "<cluster_ID>" }' \ mdb.api.cloud.yandex.net:443 \ yandex.cloud.mdb.mongodb.v1.ClusterService.GetYou can get the cluster ID from the list of clusters in your folder.
-
Check the server response to make sure your request was successful.
Viewing cluster operations
All actions performed on Yandex StoreDoc clusters are logged, with each operation assigned a unique ID.
Getting a list of operations
To view operations for all Yandex StoreDoc clusters, select
You can get a list of cluster operations as follows:
-
In the management console
, open the folder containing your cluster. -
Navigate to the Yandex StoreDoc service.
-
In the left-hand panel, select
Clusters. -
Select your cluster.
-
Navigate to the
Operations panel for the selected cluster.You will see the list of cluster operations.
If you do not have the Yandex Cloud CLI installed yet, install and initialize it.
By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.
To get a list of Yandex StoreDoc cluster operations, run this command:
yc managed-mongodb cluster list-operations <cluster_name_or_ID>
Result:
+----------------------+---------------------+----------------------+---------------------+--------+------------------------+
| ID | CREATED AT | CREATED BY | MODIFIED AT | STATUS | DESCRIPTION |
+----------------------+---------------------+----------------------+---------------------+--------+------------------------+
| c9ql1rfrqk4u******** | 2024-09-07 16:37:10 | aje9k8luj4qf******** | 2024-09-07 16:44:28 | DONE | Create MongoDB cluster |
+----------------------+---------------------+----------------------+---------------------+--------+------------------------+
You can get the cluster’s name and ID from list of clusters in your folder.
By default, operation details are displayed in text format. To get more detailed information, specify the yaml or json output format using the --format argument:
yc managed-mongodb cluster list-operations c9qk2926qqu9******** --format yaml
Result:
- id: c9ql1rfrqk4u********
description: Create MongoDB cluster
created_at: "2024-09-07T16:37:10.533508Z"
created_by: aje9k8luj4qf********
modified_at: "2024-09-07T16:44:28.147771Z"
done: true
metadata:
'@type': type.googleapis.com/yandex.cloud.mdb.mongodb.v1.CreateClusterMetadata
cluster_id: c9q8tmbam8co********
response:
'@type': type.googleapis.com/google.rpc.Status
message: OK
-
Get an IAM token for API authentication and place it in an environment variable:
export IAM_TOKEN="<IAM_token>" -
Call the Cluster.ListOperations method, e.g., via the following cURL
request:curl \ --request GET \ --header "Authorization: Bearer $IAM_TOKEN" \ --url 'https://mdb.api.cloud.yandex.net/managed-mongodb/v1/clusters/<cluster_ID>/operations'You can get the cluster ID from the list of clusters in your folder.
-
Check the server response to make sure your request was successful.
-
Get an IAM token for API authentication and place it in an environment variable:
export IAM_TOKEN="<IAM_token>" -
Clone the cloudapi
repository:cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapiBelow, we assume that the repository contents reside in the
~/cloudapi/directory. -
Call the ClusterService.ListOperations method, e.g., via the following gRPCurl
request:grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/mdb/mongodb/v1/cluster_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "cluster_id": "<cluster_ID>" }' \ mdb.api.cloud.yandex.net:443 \ yandex.cloud.mdb.mongodb.v1.ClusterService.ListOperationsYou can get the cluster ID from the list of clusters in your folder.
-
Check the server response to make sure your request was successful.
Getting operation details
-
Copy the ID of the operation you need.
-
Get operation details:
CLIREST APIgRPC APIIf you do not have the Yandex Cloud CLI installed yet, install and initialize it.
By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the
yc config set folder-id <folder_ID>command. You can also set a different folder for any specific command using the--folder-nameor--folder-idparameter.Run this command:
yc operation get <operation_ID>Result:
id: c9ql1rfrqk4u******** description: Create MongoDB cluster created_at: "2024-09-07T16:37:10.533508Z" created_by: aje9k8luj4qf******** modified_at: "2024-09-07T16:44:28.147771Z" done: true metadata: '@type': type.googleapis.com/yandex.cloud.mdb.mongodb.v1.CreateClusterMetadata cluster_id: c9q8tmbam8co******** response: '@type': type.googleapis.com/yandex.cloud.mdb.mongodb.v1.Cluster ...-
Get an IAM token for API authentication and place it in an environment variable:
export IAM_TOKEN="<IAM_token>" -
Call the Operation.Get method, e.g., via the following cURL
request:curl \ --request GET \ --header "Authorization: Bearer $IAM_TOKEN" \ --url 'https://operation.api.cloud.yandex.net/operations/<operation_ID>' -
Check the server response to make sure your request was successful.
-
Get an IAM token for API authentication and place it in an environment variable:
export IAM_TOKEN="<IAM_token>" -
Clone the cloudapi
repository:cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapiBelow, we assume that the repository contents reside in the
~/cloudapi/directory. -
Call the OperationService.Get method, e.g., via the following gRPCurl
request:grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/operation/operation_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "operation_id": "<operation_ID>" }' \ operation.api.cloud.yandex.net:443 \ yandex.cloud.operation.OperationService.Get -
Check the server response to make sure your request was successful.
-