Viewing Cloud Desktop resource operations
The system logs all actions with Cloud Desktop resources in an operation list. Each operation gets its own unique ID.
Getting a list of operations
You can get a list of operations for a specific resource. The steps below explain how to do this for a desktop. The same steps apply to other resources as well.
-
In the management console, open the folder containing the desktop.
-
Select Cloud Desktop.
-
In the left-hand panel, select Desktops.
-
Select the desktop you need.
-
Navigate to the Operations panel for the selected desktop.
You will see a list of operations with the selected desktop.
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 the Cloud Desktop resource, run this command:
yc desktops <resource_type> list-operations <resource_name_or_ID>
Example
Getting a list of operations for a desktop:
yc desktops desktop list-operations e3v7nfkhn0q4********
Result:
+----------------------+---------------------+----------------------+---------------------+---------+-----------------+
| ID | CREATED AT | CREATED BY | MODIFIED AT | STATUS | DESCRIPTION |
+----------------------+---------------------+----------------------+---------------------+---------+-----------------+
| e3vlaf6r4241******** | 2024-05-14 17:55:00 | aje9k8luj4qf******** | 2024-05-14 17:55:00 | RUNNING | Restart desktop |
| e3vns4mmfsal******** | 2024-05-14 17:41:14 | aje9k8luj4qf******** | 2024-05-14 17:45:17 | DONE | Create desktop |
+----------------------+---------------------+----------------------+---------------------+---------+-----------------+
By default, operation information is displayed as text. To get more detailed information, specify the yaml or json output data format using the --format parameter:
yc desktops desktop list-operations e3v7nfkhn0q4******** --format yaml
Result:
- id: e3vlaf6r4241********
description: Restart desktop
created_at: "2024-05-14T17:55:00.742136402Z"
created_by: aje9k8luj4qf********
modified_at: "2024-05-14T17:55:00.742136402Z"
metadata:
'@type': type.googleapis.com/yandex.cloud.clouddesktop.v1.api.RestartDesktopMetadata
desktop_id: e3v7nfkhn0q4********
- id: e3vns4mmfsal********
description: Create desktop
created_at: "2024-05-14T17:41:14.076Z"
created_by: aje9k8luj4qf********
modified_at: "2024-05-14T17:45:17.355765714Z"
done: true
metadata:
'@type': type.googleapis.com/yandex.cloud.clouddesktop.v1.api.CreateDesktopMetadata
desktop_id: e3v7nfkhn0q4********
Use the listOperations REST API method for the Desktop resource or the DesktopService/ListOperations gRPC API call.
Getting detailed information about an operation
-
Get a list of operations for the resource.
-
Copy the operation ID.
-
Get operation details:
CLIIf 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: e3vlaf6r4241******** description: Restart desktop created_at: "2024-05-14T17:55:00.742Z" created_by: aje9k8luj4qf******** modified_at: "2024-05-14T17:57:47.065Z" done: true metadata: '@type': type.googleapis.com/yandex.cloud.clouddesktop.v1.api.RestartDesktopMetadata desktop_id: e3v7nfkhn0q4******** response: '@type': type.googleapis.com/yandex.cloud.clouddesktop.v1.api.Desktop id: e3v7nfkhn0q4******** folder_id: b1g681qpemb4******** desktop_group_id: e3vud47oonha******** created_at: "2024-05-14T17:41:14.076Z" name: my-desktop-group-1fb68746******** resources: memory: "2147483648" cores: "2" core_fraction: "100" network_interfaces: - network_id: enpphqi8uvcm******** subnet_id: e9bmuh93af4v******** users: - subject_id: aje9k8luj4qf********