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
    • Yandex SIEM
    • 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 SpeechKit Hybrid
  • System requirements
  • Service architecture
    • Service settings
    • Monitoring SpeechKit Hybrid services
    • Envoy monitoring
    • Logging levels
    • TLS termination
  • API authentication
  • Pricing policy
  • SpeechKit Hybrid releases

In this article:

  • Setting the logging level when running a container
  • Setting the logging level in the docker compose file
  1. SpeechKit Hybrid administration
  2. Logging levels

Operations logging SpeechKit Hybrid

Written by
Yandex Cloud
Updated at February 20, 2023
View in Markdown
  • Setting the logging level when running a container
  • Setting the logging level in the docker compose file

You can control which SpeechKit Hybrid container actions will be written to logs. The logging level is determined by the LOGGING_LEVEL parameter.

Supported logging levels:

  • DEBUG
  • NOTICE
  • INFO (default)
  • WARNING
  • ERROR
  • EMERG
  • ALERT
  • CRITICAL_INFO

Setting the logging level when running a containerSetting the logging level when running a container

To set the logging level, assign a value to the variable when running your SpeechKit Hybrid container, for example:

docker run --network=host-e LOGGING_LEVEL=DEBUG -e LICENSE_MODE=billing_agent <license_server_image>

Setting the logging level in the docker compose fileSetting the logging level in the docker compose file

If you use Docker Compose to run your SpeechKit Hybrid containers, you can set the logging level for each container in the configuration file.

For example, the following configuration will set the logging levels: INFO for the billing_agent container, NOTICE for the license server, and WARNING for the envoy container.

version: '3'
services:
  billing_agent:
    network_mode: host
    volumes:
      - persistent:/var/swaydb
    environment:
      LOGGING_LEVEL: INFO
      STATIC_API_KEY: XXX
    image: billing_agent:0.15
  license_server:
    network_mode: host
    environment:
      LICENSE_MODE: billing_agent
      LOGGING_LEVEL: NOTICE
    image: license-server:0.15
    depends_on:
      - billing_agent
  envoy:
    network_mode: host
    environment:
      LOGGING_LEVEL: WARNING
      ENVOY_UID: 0      
    image: envoy:0.15
    depends_on:
      - license_server

Was the article helpful?

Previous
Envoy monitoring
Next
TLS termination
© 2026 Direct Cursus Technology L.L.C.