Viewing operations with Serverless Integrations resources
The system logs all actions with Serverless Integrations resources as a list of operations. Each operation gets its own unique ID.
Getting a list of operations
You can get a list of operations for a specific resource. Follow the steps below to do this for an EventRouter bus. The same steps apply to other resources as well.
-
In the management console
, open the folder the bus resides in. -
Select Serverless Integrations.
-
In the left-hand panel, select
EventRouter. -
Select a bus.
-
Go to the
Operations panel for the selected bus.You will see a list of operations with the bus.
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 Serverless Integrations resource, run this command:
yc serverless <resource_type> list-operations <resource_name_or_ID>
Example
Getting a list of operations for an EventRouter bus:
yc serverless eventrouter bus list-operations epdplu8jn7sr********
Result:
+----------------------+---------------------+----------------------+---------------------+--------+----------------+
| ID | CREATED AT | CREATED BY | MODIFIED AT | STATUS | DESCRIPTION |
+----------------------+---------------------+----------------------+---------------------+--------+----------------+
| f66oon77ahgu******** | 2025-02-24 20:48:53 | ajevfb0tjfts******** | 2025-02-24 20:48:53 | DONE | Updating a bus |
| f66a237f2f6v******** | 2025-02-24 20:48:30 | ajevfb0tjfts******** | 2025-02-24 20:48:30 | DONE | Updating a bus |
| f66cbrh8c1u4******** | 2025-02-20 12:22:56 | ajevfb0tjfts******** | 2025-02-20 12:22:57 | DONE | Creating a bus |
+----------------------+---------------------+----------------------+---------------------+--------+----------------+
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 serverless eventrouter bus list-operations <bus_name_or_ID> --format yaml
Result:
- id: f66oon77ahgu********
description: Updating a bus
created_at: "2025-02-24T20:48:53.942469190Z"
created_by: ajevfb0tjfts********
modified_at: "2025-02-24T20:48:53.956957528Z"
done: true
metadata:
'@type': type.googleapis.com/yandex.cloud.serverless.eventrouter.v1.UpdateBusMetadata
bus_id: f662ctjn8vv4********
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 an EventRouter bus, use the listOperations REST API method for the Bus resource or the BusService/ListOperations gRPC API call.
Getting operation details
-
Copy the ID of the operation you need.
-
Get operation details:
CLIAPIIf 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: f66oon77ahgu******** description: Updating a bus created_at: "2025-02-24T20:48:53.942Z" created_by: ajevfb0tjfts******** modified_at: "2025-02-24T20:48:53.956Z" done: true metadata: '@type': type.googleapis.com/yandex.cloud.serverless.eventrouter.v1.UpdateBusMetadata bus_id: f662ctjn8vv4******** response: '@type': type.googleapis.com/yandex.cloud.serverless.eventrouter.v1.Bus id: f662ctjn8vv4******** folder_id: b1geoelk7fld******** cloud_id: b1gia87mbaom******** created_at: "2025-02-20T12:22:57.005054Z" name: test description: tesst status: ACTIVETo get detailed information about an operation, use the
getREST API method for theOperationresource or theOperationService/GetgRPC API call.