[Yandex Cloud documentation](../../index.md) > [Yandex Serverless Integrations](../index.md) > [Step-by-step guides](index.md) > Viewing operations with service resources

# Viewing operations with Serverless Integrations resources

The system logs all actions with Serverless Integrations resources as a list of operations. Each operation gets an 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. Follow the steps below to do this for an EventRouter bus. The same steps apply to other resources as well.

  1. In the [management console](https://console.yandex.cloud), open the folder the bus resides in.
  1. Navigate to **Serverless Integrations**.
  1. In the left-hand panel, select ![image](../../_assets/console-icons/object-align-center-vertical.svg) **EventRouter**.
  1. Select a bus.
  1. Go to the ![image](../../_assets/console-icons/list-check.svg) **Operations** panel for the selected bus.

     You will see the list of operations with the bus.

- 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 <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 Serverless Integrations resource, run this command:

  ```bash
  yc serverless <resource_type> list-operations <resource_name_or_ID>
  ```

  **Example**

  Getting a list of operations for an EventRouter bus:

  ```bash
  yc serverless eventrouter bus list-operations epdplu8jn7sr********
  ```

  Result:

  ```text
  +----------------------+---------------------+----------------------+---------------------+--------+----------------+
  |          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, information about operations is output as text. To get more details, use `--format` to specify the `yaml` or `json` output format:

  ```bash
  yc serverless eventrouter bus list-operations <bus_name_or_ID> --format yaml
  ```

  Result:

  ```yaml
  - 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: {}
  ...
  ```

- API {#api}

  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](../eventrouter/api-ref/Bus/listOperations.md) REST API method for the [Bus](../eventrouter/api-ref/Bus/index.md) resource or the [BusService/ListOperations](../eventrouter/api-ref/grpc/Bus/listOperations.md) gRPC API call.

{% endlist %}

## Getting operation details {#get-operations-info}

1. [Get a list of operations](#get-operations).
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 <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 <operation_ID>
      ```

      Result:

      ```text
      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: ACTIVE
      ```

    - API {#api}

      To get detailed information about an operation, use the `get` REST API method for the `Operation` resource or the `OperationService/Get` gRPC API call.

    {% endlist %}

#### Useful links {#see-also}

* [Working with operations](../../api-design-guide/concepts/about-async.md)