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 IoT Core
  • Access management
  • Pricing policy
  • Terraform reference
    • Authentication with the API
      • Overview
        • Overview
        • Get
        • GetByName
        • List
        • Create
        • Update
        • Delete
        • ListCertificates
        • AddCertificate
        • DeleteCertificate
        • ListPasswords
        • AddPassword
        • DeletePassword
        • ListDeviceTopicAliases
        • ListDataStreamExports
        • AddDataStreamExport
        • DeleteDataStreamExport
        • ListOperations
        • Disable
        • Enable
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • gRPC request
  • GetRegistryRequest
  • Registry
  • LogOptions
  1. Devices API reference
  2. gRPC
  3. Registry
  4. Get

IoT Core Service, gRPC: RegistryService.Get

Written by
Yandex Cloud
Updated at December 17, 2024
  • gRPC request
  • GetRegistryRequest
  • Registry
  • LogOptions

Returns the specified registry.

To get the list of available registries, make a List request.

gRPC request

rpc Get (GetRegistryRequest) returns (Registry)

GetRegistryRequest

{
  "registry_id": "string"
}

Field

Description

registry_id

string

Required field. ID of the registry to return.

To get a registry ID make a RegistryService.List request.

Registry

{
  "id": "string",
  "folder_id": "string",
  "created_at": "google.protobuf.Timestamp",
  "name": "string",
  "description": "string",
  "labels": "map<string, string>",
  "status": "Status",
  "log_group_id": "string",
  "log_options": {
    "disabled": "bool",
    // 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"
  }
}

A registry. For more information, see Registry.

Field

Description

id

string

ID of the registry.

folder_id

string

ID of the folder that the registry belongs to.

created_at

google.protobuf.Timestamp

Creation timestamp.

name

string

Name of the registry. The name is unique within the folder.

description

string

Description of the registry. 0-256 characters long.

labels

object (map<string, string>)

Resource labels as key:value pairs. Maximum of 64 per resource.

status

enum Status

Status of the registry.

  • STATUS_UNSPECIFIED
  • CREATING: Registry is being created.
  • ACTIVE: Registry is ready to use.
  • DELETING: Registry is being deleted.
  • DISABLED: Registry is disabled.

log_group_id

string

ID of the logs group for the specified registry.

log_options

LogOptions

Options for logging registry events

LogOptions

Field

Description

disabled

bool

Is logging from registry disabled.

log_group_id

string

Entry should 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 should 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.

Was the article helpful?

Previous
Overview
Next
GetByName
© 2025 Direct Cursus Technology L.L.C.