[Yandex Cloud documentation](../../index.md) > [Yandex MPP Analytics for PostgreSQL](../index.md) > [Step-by-step guides](index.md) > Logs and monitoring > Viewing cluster operations # Viewing operations with clusters All actions with Yandex MPP Analytics for PostgreSQL clusters are logged as a list of operations. Each operation gets its own unique ID. ## Getting a list of operations {#get-operations} {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), open the folder containing the cluster. 1. Navigate to **Yandex MPP Analytics for PostgreSQL**. 1. In the left-hand panel, select ![image](../../_assets/console-icons/cubes-3.svg) **Clusters**. 1. Select the cluster and open the ![image](../../_assets/console-icons/list-check.svg) **Operations** tab. You will see the list of operations with the cluster. - CLI {#cli} If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install). The folder used by default is the one specified when [creating](../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id ` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions. To get a list of operations for a Yandex MPP Analytics for PostgreSQL cluster, run this command: ```bash yc managed-greenplum cluster list-operations ``` Result: ```text +----------------------+---------------------+----------------------+---------------------+--------+--------------------------+ | ID | CREATED AT | CREATED BY | MODIFIED AT | STATUS | DESCRIPTION | +----------------------+---------------------+----------------------+---------------------+--------+--------------------------+ | dqh0ntf6batm******** | 2024-09-07 16:36:46 | aje9k8luj4qf******** | 2024-09-07 16:44:12 | DONE | Create Greenplum cluster | +----------------------+---------------------+----------------------+---------------------+--------+--------------------------+ ``` You can get the cluster ID and name with the [list of clusters in the folder](#list-clusters). By default, information about operations is output as text. To get more details, specify the `yaml` or `json` output data format using `--format`: ```bash yc managed-greenplum cluster list-operations c9qk2926qqu9******** --format yaml ``` Result: ```text - id: dqh0ntf6batm******** description: Create Greenplum cluster created_at: "2024-09-07T16:36:46.816682Z" created_by: aje9k8luj4qf******** modified_at: "2024-09-07T16:44:12.944302Z" done: true metadata: '@type': type.googleapis.com/yandex.cloud.mdb.greenplum.v1.CreateClusterMetadata cluster_id: c9q13q0acgv7******** response: '@type': type.googleapis.com/google.rpc.Status message: OK ``` - REST API {#api} 1. [Get an IAM token for API authentication](../api-ref/authentication.md) and put it into an environment variable: ```bash export IAM_TOKEN="" ``` 1. Call the [Cluster.ListOperations](../api-ref/Cluster/listOperations.md) method, e.g., via the following [cURL](https://curl.se/) request: ```bash curl \ --request GET \ --header "Authorization: Bearer $IAM_TOKEN" \ --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/clusters//operations' ``` You can get the cluster ID with the [list of clusters in the folder](#list-clusters). 1. Check the [server response](../api-ref/Cluster/listOperations.md#yandex.cloud.mdb.greenplum.v1.ListClusterOperationsResponse) to make sure your request was successful. - gRPC API {#grpc-api} 1. [Get an IAM token for API authentication](../api-ref/authentication.md) and put it into an environment variable: ```bash export IAM_TOKEN="" ``` 1. Clone the [cloudapi](https://github.com/yandex-cloud/cloudapi) repository: ```bash cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi ``` Below, we assume that the repository contents reside in the `~/cloudapi/` directory. 1. Call the [ClusterService.ListOperations](../api-ref/grpc/Cluster/listOperations.md) method, e.g., via the following [gRPCurl](https://github.com/fullstorydev/grpcurl) request: ```bash grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/cluster_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "cluster_id": "" }' \ mdb.api.cloud.yandex.net:443 \ yandex.cloud.mdb.greenplum.v1.ClusterService.ListOperations ``` You can get the cluster ID with the [list of clusters in the folder](#list-clusters). 1. Check the [server response](../api-ref/grpc/Cluster/listOperations.md#yandex.cloud.mdb.greenplum.v1.ListClusterOperationsResponse) to make sure your request was successful. {% endlist %} ## Getting operation details {#get-operations-info} 1. [Get the list of operations](#get-operations) for the cluster. 1. Copy the ID of the operation you need. 1. Get the operation details: {% list tabs group=instructions %} - CLI {#cli} If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install). The folder used by default is the one specified when [creating](../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id ` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions. Run this command: ```bash yc operation get ``` Result: ```text id: dqh0ntf6batm******** description: Create Greenplum cluster created_at: "2024-09-07T16:36:46.816682Z" created_by: aje9k8luj4qf******** modified_at: "2024-09-07T16:44:12.944302Z" done: true metadata: '@type': type.googleapis.com/yandex.cloud.mdb.greenplum.v1.CreateClusterMetadata cluster_id: c9q13q0acgv7******** response: '@type': type.googleapis.com/yandex.cloud.mdb.greenplum.v1.Cluster ... ``` - REST API {#api} 1. [Get an IAM token for API authentication](../api-ref/authentication.md) and put it into an environment variable: ```bash export IAM_TOKEN="" ``` 1. Call the [Operation.Get](../api-ref/Operation/get.md) method, e.g., via the following [cURL](https://curl.se/) request: ```bash curl \ --request GET \ --header "Authorization: Bearer $IAM_TOKEN" \ --url 'https://operation.api.cloud.yandex.net/operations/' ``` 1. Check the [server response](../api-ref/Operation/get.md#yandex.cloud.operation.Operation) to make sure your request was successful. - gRPC API {#grpc-api} 1. [Get an IAM token for API authentication](../api-ref/authentication.md) and put it into an environment variable: ```bash export IAM_TOKEN="" ``` 1. Clone the [cloudapi](https://github.com/yandex-cloud/cloudapi) repository: ```bash cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi ``` Below, we assume that the repository contents reside in the `~/cloudapi/` directory. 1. Call the [OperationService.Get](../api-ref/grpc/Operation/get.md) method, e.g., via the following [gRPCurl](https://github.com/fullstorydev/grpcurl) request: ```bash 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.api.cloud.yandex.net:443 \ yandex.cloud.operation.OperationService.Get ``` 1. Check the [server response](../api-ref/grpc/Operation/get.md#yandex.cloud.operation.Operation) to make sure your request was successful. {% endlist %} ## See also {#see-also} * [Working with operations](../../api-design-guide/concepts/about-async.md) _Greenplum® and Greenplum Database® are registered trademarks or trademarks of Broadcom Inc. in the United States and/or other countries._