Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Serverless Integrations
  • Pricing policy
  • Terraform reference
    • API authentication
      • Overview
        • Overview
        • Get
        • List
        • Create
        • Update
        • Delete
        • ListOperations
        • ListAccessBindings
        • SetAccessBindings
        • UpdateAccessBindings
  • Release notes

In this article:

  • gRPC request
  • ListBusesRequest
  • ListBusesResponse
  • Bus
  • LogOptions
  1. EventRouter API reference
  2. gRPC
  3. Bus
  4. List

EventRouter Service, gRPC: BusService.List

Written by
Yandex Cloud
Updated at April 24, 2025
  • gRPC request
  • ListBusesRequest
  • ListBusesResponse
  • Bus
  • LogOptions

Retrieves the list of buses in the specified folder.

gRPC requestgRPC request

rpc List (ListBusesRequest) returns (ListBusesResponse)

ListBusesRequestListBusesRequest

{
  "folder_id": "string",
  "page_size": "int64",
  "page_token": "string",
  "filter": "string"
}

Field

Description

folder_id

string

Required field. ID of the folder to list buses in.

page_size

int64

Maximum number of buses to return.

page_token

string

Page token. To get the next page of results, set page_token to the
ListBusesResponse.next_page_token returned by a previous list request.

filter

string

Supported fields for filter:
name
created_at

ListBusesResponseListBusesResponse

{
  "buses": [
    {
      "id": "string",
      "folder_id": "string",
      "cloud_id": "string",
      "created_at": "google.protobuf.Timestamp",
      "name": "string",
      "description": "string",
      "labels": "map<string, string>",
      "deletion_protection": "bool",
      "status": "Status",
      "logging_enabled": "bool",
      "log_options": {
        // Includes only one of the fields `log_group_id`, `folder_id`
        "log_group_id": "string",
        "folder_id": "string",
        // end of the list of possible fields
        "min_level": "Level",
        "service_account_id": "string"
      }
    }
  ],
  "next_page_token": "string"
}

Field

Description

buses[]

Bus

List of buses.

next_page_token

string

Token for getting the next page of the list of buses.

BusBus

Field

Description

id

string

ID of the bus.

folder_id

string

ID of the folder that the bus belongs to.

cloud_id

string

ID of the cloud that the bus resides in.

created_at

google.protobuf.Timestamp

Creation timestamp.

name

string

Name of the bus.

description

string

Description of the bus.

labels

object (map<string, string>)

Resource labels as key:value pairs.

deletion_protection

bool

Deletion protection.

status

enum Status

Status of the bus.

  • STATUS_UNSPECIFIED
  • CREATING
  • ACTIVE
  • DELETING

logging_enabled

bool

Is logging from the bus enabled.

log_options

LogOptions

Options for logging from the bus.

LogOptionsLogOptions

Field

Description

log_group_id

string

Entry will be written to log group resolved by ID.

Includes only one of the fields log_group_id, folder_id.

Log entries destination.

folder_id

string

Entry will be written to default log group for specified folder.

Includes only one of the fields log_group_id, folder_id.

Log entries destination.

min_level

enum Level

Minimum log entry level.

See LogLevel.Level for details.

  • LEVEL_UNSPECIFIED: Default log level.

    Equivalent to not specifying log level at all.

  • TRACE: Trace log level.

    Possible use case: verbose logging of some business logic.

  • DEBUG: Debug log level.

    Possible use case: debugging special cases in application logic.

  • INFO: Info log level.

    Mostly used for information messages.

  • WARN: Warn log level.

    May be used to alert about significant events.

  • ERROR: Error log level.

    May be used to alert about errors in infrastructure, logic, etc.

  • FATAL: Fatal log level.

    May be used to alert about unrecoverable failures and events.

service_account_id

string

Required field. Service account, which has permission to write to destination

Was the article helpful?

Previous
Get
Next
Create
© 2025 Direct Cursus Technology L.L.C.