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

# Viewing operations with Cloud Functions resources

The system logs all actions with Cloud Functions 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 a function. The same steps apply to other resources.

  1. In the [management console](https://console.yandex.cloud), open the folder with the function.
  1. Navigate to **Cloud Functions**.
  1. In the left-hand panel, select ![image](../../_assets/console-icons/curly-brackets-function.svg) **Functions**.
  1. Select the function.
  1. Go to the ![image](../../_assets/console-icons/list-check.svg) **Operations** panel for the selected function.

     You will see a list of operations with the selected function.

- 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 Cloud Functions resource, run this command:

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

  **Example**

  Getting a list of operations for a function:

  ```bash
  yc serverless function list-operations epdplu8jn7sr********
  ```

  Result:

  ```text
  +----------------------+---------------------+----------------------+---------------------+--------+-----------------+
  |          ID          |     CREATED AT      |      CREATED BY      |     MODIFIED AT     | STATUS |   DESCRIPTION   |
  +----------------------+---------------------+----------------------+---------------------+--------+-----------------+
  | d4e952nebqdb******** | 2024-06-19 08:33:11 | aje9k8luj4qf******** | 2024-06-19 08:33:12 | DONE   | Create session  |
  | d4elh7hqnj7g******** | 2024-06-19 08:33:04 | aje9k8luj4qf******** | 2024-06-19 08:33:04 | DONE   | Create function |
  +----------------------+---------------------+----------------------+---------------------+--------+-----------------+
  ```

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

  ```bash
  yc serverless function list-operations <resource_name_or_ID> --format yaml
  ```

  Result:

  ```text
  - id: d4e952nebqdb********
    description: Create session
    created_at: "2024-06-19T08:33:11.658Z"
    created_by: aje9k8luj4qf********
    modified_at: "2024-06-19T08:33:12.345Z"
    done: true
    metadata:
      '@type': type.googleapis.com/google.protobuf.Empty
      value: {}
    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 a function, use either the [listOperations](../functions/api-ref/Function/listOperations.md) REST API method for the [Function](../functions/api-ref/Function/index.md) resource or the [FunctionService/ListOperations](../functions/api-ref/grpc/Function/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 <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: d4elh7hqnj7g********
        description: Create function
        created_at: "2024-06-19T08:33:04.513Z"
        created_by: aje9k8luj4qf********
        modified_at: "2024-06-19T08:33:04.665Z"
        done: true
        metadata:
          '@type': type.googleapis.com/yandex.cloud.serverless.functions.v1.CreateFunctionMetadata
          function_id: d4e3f75v8kti********
        response:
          '@type': type.googleapis.com/yandex.cloud.serverless.functions.v1.Function
          id: d4e3f75v8kti********
          folder_id: b1g681qpemb4********
          created_at: "2024-06-19T08:33:04.587Z"
          name: my-db-function
          http_invoke_url: https://functions.yandexcloud.net/d4e3f75v8kti********
          status: ACTIVE
      ```

    - API {#api}

      Use the [OperationService/Get](../functions/api-ref/grpc/Operation/get.md) gRPC API call.

    {% endlist %}

#### See also {#see-also}

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