Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex MPP Analytics for PostgreSQL
  • Getting started
    • All guides
    • Connecting to an external file server (gpfdist)
      • Viewing cluster logs
      • Viewing cluster operations
      • Performance diagnostics
      • Monitoring the state of clusters and hosts
      • Transferring cluster logs to Yandex Cloud Logging
    • Auxiliary utilities
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Getting a list of operations
  • Getting operation details
  • See also
  1. Step-by-step guides
  2. Logs and monitoring
  3. Viewing cluster operations

Viewing operations with clusters

Written by
Yandex Cloud
Updated at November 26, 2025
  • Getting a list of operations
  • Getting operation details
  • See also

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 operationsGetting a list of operations

Management console
CLI
REST API
gRPC API
  1. In the management console, open the folder with the cluster.

  2. Select Yandex MPP Analytics for PostgreSQL.

  3. In the left-hand panel, select Clusters.

  4. Select the cluster you need.

  5. Navigate to the Operations panel for the cluster you selected.

    You will see a list of operations with the cluster you selected.

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 the list of operations for a Yandex MPP Analytics for PostgreSQL cluster, run this command:

yc managed-greenplum cluster list-operations <cluster_name_or_ID>

Result:

+----------------------+---------------------+----------------------+---------------------+--------+--------------------------+
|          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.

By default, information about operations is displayed as text. To get more detailed information, specify the yaml or json output data format using the --format parameter:

yc managed-greenplum cluster list-operations c9qk2926qqu9******** --format yaml

Result:

- 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
  1. Get an IAM token for API authentication and set it as an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. 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-greenplum/v1/clusters/<cluster_ID>/operations'
    

    You can get the cluster ID with the list of clusters in the folder.

  3. Check the server response to make sure your request was successful.

  1. Get an IAM token for API authentication and set it as an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

  3. Use the ClusterService.ListOperations call and send the following request, e.g., via gRPCurl:

    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": "<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.

  4. Check the server response to make sure your request was successful.

Getting operation detailsGetting operation details

  1. Get the list of operations for the cluster.

  2. Copy the ID of the operation you need.

  3. Get the operation details:

    CLI
    REST API
    gRPC API

    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.

    Run this command:

    yc operation get <operation_ID>
    

    Result:

    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
    ...
    
    1. Get an IAM token for API authentication and set it as an environment variable:

      export IAM_TOKEN="<IAM_token>"
      
    2. 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>'
      
    3. Check the server response to make sure your request was successful.

    1. Get an IAM token for API authentication and set it as an environment variable:

      export IAM_TOKEN="<IAM_token>"
      
    2. Clone the cloudapi repository:

      cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
      

      Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

    3. Use the OperationService.Get call and send the following request, e.g., via gRPCurl:

      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
      
    4. Check the server response to make sure your request was successful.

See alsoSee also

  • Working with operations

Greenplum® and Greenplum Database® are registered trademarks or trademarks of Broadcom Inc. in the United States and/or other countries.

Was the article helpful?

Previous
Viewing cluster logs
Next
Performance diagnostics
© 2025 Direct Cursus Technology L.L.C.