[Yandex Cloud documentation](../../index.md) > [Yandex Application Load Balancer](../index.md) > [Step-by-step guides](index.md) > Viewing service resource operations # Viewing operations with Application Load Balancer resources The system logs all actions with Application Load Balancer resources 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} You can get a list of operations for a specific resource. The steps below describe how you can do this for an [L7 load balancer](../concepts/application-load-balancer.md). The same steps apply to other resources as well. 1. In the [management console](https://console.yandex.cloud), select the folder with your load balancer. 1. Navigate to **Application Load Balancer**. 1. In the left-hand panel, select ![image](../../_assets/console-icons/branches-down.svg) **Load balancers**. 1. Select the load balancer you need. 1. Navigate to the ![image](../../_assets/console-icons/list-check.svg) **Operations** panel for the selected load balancer. You will see a list of operations with the selected load balancer. - 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 the list of operations for the Application Load Balancer resource, run this command: ```bash yc alb list-operations ``` **Example** Getting a list of operations for a load balancer: ```bash yc alb load-balancer list-operations ds7857cmjtuv******** ``` Result: ```text +----------------------+---------------------+----------------------+---------------------+--------+--------------------------------+ | ID | CREATED AT | CREATED BY | MODIFIED AT | STATUS | DESCRIPTION | +----------------------+---------------------+----------------------+---------------------+--------+--------------------------------+ | ds71vdf0jqut******** | 2024-05-14 14:36:06 | aje9k8luj4qf******** | 2024-05-14 14:36:06 | DONE | update loadbalancer | | | | | | | 'ds7857cmjtuv********' | | ds7nspb18tkg******** | 2024-05-14 12:29:53 | aje9k8luj4qf******** | 2024-05-14 12:34:46 | DONE | create loadbalancer | | | | | | | 'ds7857cmjtuv********' | +----------------------+---------------------+----------------------+---------------------+--------+--------------------------------+ ``` By default, information about operations is output as text. To get more details, use `--format` to specify the `yaml` or `json` output format: ```bash yc alb load-balancer list-operations ds7857cmjtuv******** --format yaml ``` Result: ```text - id: ds71vdf0jqut******** description: update loadbalancer 'ds7857cmjtuv********' created_at: "2024-05-14T14:36:06.637766633Z" created_by: aje9k8luj4qf******** modified_at: "2024-05-14T14:36:06.666429213Z" done: true metadata: '@type': type.googleapis.com/yandex.cloud.apploadbalancer.v1.UpdateLoadBalancerMetadata load_balancer_id: ds7857cmjtuv******** response: '@type': type.googleapis.com/yandex.cloud.apploadbalancer.v1.LoadBalancer id: ds7857cmjtuv******** name: my-alb folder_id: b1g681qpemb4******** status: ACTIVE ... created_at: "2024-05-14T12:29:53.571411960Z" log_options: {} - id: ds7nspb18tkg******** description: create loadbalancer 'ds7857cmjtuv********' created_at: "2024-05-14T12:29:53.571411960Z" created_by: aje9k8luj4qf******** modified_at: "2024-05-14T12:34:46.963930680Z" done: true metadata: '@type': type.googleapis.com/yandex.cloud.apploadbalancer.v1.CreateLoadBalancerMetadata load_balancer_id: ds7857cmjtuv******** response: '@type': type.googleapis.com/yandex.cloud.apploadbalancer.v1.LoadBalancer id: ds7857cmjtuv******** name: my-alb folder_id: b1g681qpemb4******** status: ACTIVE ... created_at: "2024-05-14T12:29:53.571411960Z" log_options: {} ``` - API {#api} Use the `listOperations` REST API method for the relevant resource or the `/ListOperations` gRPC API call. For example, for a load balancer, use either the [listOperations](../api-ref/LoadBalancer/listOperations.md) REST API method for the [LoadBalancer](../api-ref/LoadBalancer/index.md) resource or the [LoadBalancerService/ListOperations](../api-ref/grpc/LoadBalancer/listOperations.md) gRPC API call. {% endlist %} ## Getting operation details {#get-operations-info} 1. [Get the list of operations](#get-operations) for the resource. 1. Copy the operation ID. 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 ``` ```yaml id: ds7nspb18tkg******** description: create loadbalancer 'ds7857cmjtuv********' created_at: "2024-05-14T12:29:53.571411960Z" created_by: aje9k8luj4qf******** modified_at: "2024-05-14T12:34:46.963930680Z" done: true metadata: '@type': type.googleapis.com/yandex.cloud.apploadbalancer.v1.CreateLoadBalancerMetadata load_balancer_id: ds7857cmjtuv******** response: '@type': type.googleapis.com/yandex.cloud.apploadbalancer.v1.LoadBalancer id: ds7857cmjtuv******** name: my-alb folder_id: b1g681qpemb4******** status: ACTIVE region_id: ru-central1 network_id: enp3srbi9u49******** allocation_policy: locations: - zone_id: ru-central1-a subnet_id: e9bpric55er9******** - zone_id: ru-central1-b subnet_id: e2l15qssjar5******** - zone_id: ru-central1-d subnet_id: fl85ebb396ub******** created_at: "2024-05-14T12:29:53.571411960Z" log_options: {} ``` - API {#api} Use the [OperationService/Get](../api-ref/grpc/Operation/get.md) gRPC API call. {% endlist %} #### Useful links {#see-also} * [Working with operations](../../api-design-guide/concepts/about-async.md)