Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Compute Cloud
    • All guides
    • Viewing operations with resources
    • Viewing metrics Monitoring
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
  • Metrics Monitoring
  • Audit Trails events
  • Release notes

In this article:

  • Getting a list of operations
  • Getting operation details
  1. Step-by-step guides
  2. Viewing operations with resources

Viewing operations with Compute Cloud resources

Written by
Yandex Cloud
Updated at July 31, 2026
View in Markdown
  • Getting a list of operations
  • Getting operation details

The system logs all actions with Compute Cloud resources as a list of operations. Each operation gets its own unique ID.

Getting a list of operationsGetting a list of operations

Note

Compute Cloud stores data on resource operations for the last two weeks.

Management console
CLI
API

To view operations with all the resources, select Operations in the left-hand panel. This will open the list of all operations, including those on currently deleted resources.

You can get a list of operations for a specific resource. The steps below describe how you can do this for a VM. The same steps apply to other resources as well.

  1. In the management console, open the folder with the VM.

  2. Navigate to Compute Cloud.

  3. In the left-hand panel, select Virtual machines.

  4. Select the VM.

  5. Go to the Operations panel for the selected VM.

    This will open the list of operations with the VM and resources connected to it.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <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 the list of operations for the Compute Cloud resource, run this command:

yc compute <resource_type> list-operations <resource_name_or_ID>

Example

Getting a list of operations for a VM:

yc compute instance list-operations epdplu8jn7sr********

Result:

+----------------------+---------------------+----------------------+---------------------+--------+-----------------+
|          ID          |     CREATED AT      |      CREATED BY      |     MODIFIED AT     | STATUS |   DESCRIPTION   |
+----------------------+---------------------+----------------------+---------------------+--------+-----------------+
| epd2ohv6ur6a******** | 2023-10-20 08:34:01 | ajeef73j5iq9******** | 2023-10-20 08:34:05 | DONE   | Update instance |
| epd2lcg5na2r******** | 2023-10-20 08:32:28 | ajeef73j5iq9******** | 2023-10-20 08:32:55 | DONE   | Stop instance   |
+----------------------+---------------------+----------------------+---------------------+--------+-----------------+

By default, information about operations is output as text. To get more details, use --format to specify the yaml or json output format:

yc compute instance list-operations epdplu8jn7sr******** --format yaml

Result:

- id: epd2ohv6ur6a********
  description: Update instance
  created_at: "2023-10-20T08:34:01Z"
  created_by: ajeef73j5iq9********
  modified_at: "2023-10-20T08:34:05Z"
  done: true
  metadata:
    '@type': type.googleapis.com/yandex.cloud.compute.v1.UpdateInstanceMetadata
    instance_id: epdplu8jn7sr********
  response:
    '@type': type.googleapis.com/yandex.cloud.compute.v1.Instance
    id: epdplu8jn7sr********
    folder_id: b1g86q4m5vej********
    created_at: "2023-10-02T13:19:45Z"
    name: rewq
    zone_id: ru-central1-a
    platform_id: standard-v3
    resources:
      memory: "2147483648"
      cores: "2"
      core_fraction: "100"
    status: STOPPED
    ...
- id: epd2lcg5na2r********
  description: Stop instance
  created_at: "2023-10-20T08:32:28Z"
  created_by: ajeef73j5iq9********
  modified_at: "2023-10-20T08:32:55Z"
  done: true
  metadata:
    '@type': type.googleapis.com/yandex.cloud.compute.v1.StopInstanceMetadata
    instance_id: epdplu8jn7sr********
  response:
    '@type': type.googleapis.com/google.protobuf.Empty
    value: {}

Use the listOperations REST API method for the relevant resource or the <service>/ListOperations gRPC API call.

For example, for a VM, use either the listOperations REST API method for the Instance resource or the InstanceService/ListOperations gRPC API call.

Getting operation detailsGetting operation details

  1. Get the list of operations for the resource.

  2. Copy the operation ID.

  3. Get the operation details:

    CLI
    API

    If you do not have the Yandex Cloud CLI yet, install and initialize it.

    The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <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:

    yc operation get <operation_ID>
    

    Result:

    id: ef3ovrdqhhf9********
    description: Delete instance
    created_at: "2023-10-17T16:08:10Z"
    created_by: ajejisqqifen********
    modified_at: "2023-10-17T16:08:41Z"
    done: true
    metadata:
      '@type': type.googleapis.com/yandex.cloud.compute.v1.DeleteInstanceMetadata
      instance_id: ef3su74qmfp4********
    response:
      '@type': type.googleapis.com/google.protobuf.Empty
      value: {}
    

    Use the get REST API method for the Operation resource or the OperationService/Get gRPC API call.

Useful linksUseful links

  • Working with operations

Was the article helpful?

Previous
Managing instances in a pool
Next
Viewing metrics Monitoring
© 2026 Direct Cursus Technology L.L.C.