Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Application Load Balancer
  • Getting started
    • All guides
    • Creating Application Load Balancer infrastructure through a wizard
      • Creating an L7 load balancer
      • Editing an L7 load balancer
      • Getting information about an L7 load balancer
      • Viewing L7 load balancer statistics
      • Setting up alerts
      • Viewing L7 load balancer logs
      • Setting up L7 load balancer logging
      • Getting a log group ID of an L7 load balancer
      • Stopping and starting an L7 load balancer
      • Moving a VM to a target group in a different availability zone
      • Deleting an L7 load balancer
    • Viewing service resource operations
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • L7 load balancer logs
  • Release notes
  1. Step-by-step guides
  2. L7 load balancers
  3. Getting a log group ID of an L7 load balancer

Getting a log group ID of an L7 load balancer

Written by
Yandex Cloud
Updated at June 29, 2026
View in Markdown

To get the ID of the Yandex Cloud Logging log group receiving logs from the L7 load balancer:

Management console
CLI
API
  1. In the management console, select the folder the load balancer is in.
  2. Navigate to Application Load Balancer.
  3. Click your load balancer's name.
  4. Under Log settings, click the log group name in the Cloud Logging log group field.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating 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.

  1. See the description of the CLI command to get information about an L7 load balancer:

    yc alb load-balancer get --help
    
  2. Run this command with your load balancer name specified:

    yc alb load-balancer get <load_balancer_name>
    

    Result:

    id: a5d88ep483cm********
    name: test-balancer2
    folder_id: aoe197919j8e********
    status: ACTIVE
    region_id: ru-central1
    network_id: c64l1c06d151********
    allocation_policy:
      locations:
      - zone_id: ru-central1-a
        subnet_id: buc4gsmpj8hv********
    log_group_id: eolul9ap0bv0********
    created_at: "2021-04-26T12:12:13.624832586Z"
    log_options:
      log_group_id: e23ujjda632o********
    

    You will see the Cloud Logging log group ID in the log_group_id field under log_options. Note that the log_group_id field following the subnet_id field contains a different ID referring to the outdated logging service.

Use the get REST API method for the LoadBalancer resource or the LoadBalancerService/Get gRPC API call.

You will see the Cloud Logging log group ID in the logGroupId field under logOptions. Note that the logGroupId field outside logOptions contains a different ID referring to the outdated logging service.

If you kept the Default log group value in the Cloud Logging log group field when creating an L7 load balancer, do the following to get its ID:

Management console
CLI
  1. In the management console, navigate to the folder with your load balancer.
  2. Navigate to Cloud Logging.
  3. Save the default log group ID.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating 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 default log group ID, run this command:

yc logging group get \
  --name=default \
  --folder-id=<folder_ID>

Where:

  • --name: Default log group name, i.e., default.
  • --folder-id: ID of the folder with your load balancer.

Result:

id: e23qfbb01na0********
folder_id: b1gvgqhc5745********
cloud_id: b1g3clmedscm********
created_at: "2021-08-07T10:40:55.412Z"
name: default
description: Auto-created default group

Was the article helpful?

Previous
Setting up L7 load balancer logging
Next
Stopping and starting an L7 load balancer
© 2026 Direct Cursus Technology L.L.C.