Migrating from Cloud Logging to Monium

Cloud Logging and Monium comparisonCloud Logging and Monium comparison

All prices are shown in the Cloud Logging and Monium pricing policies.

Testing Monium without migrationTesting Monium without migration

Logs from Cloud Logging are already available in Monium. Open them in the management console in one of the following ways:

• When viewing logs in Cloud Logging, click Open in Monium.

• Open the link:

  https://monium.yandex.cloud/projects/folder__<folder_ID>/logs
  

For each folder, a project with an ID in folder__<folder_ID> format is created, and logs of every log group can be accessed by its name.

To search for logs, specify a request like:

{project="folder__<folder_ID>", cluster="default", service="<log_group_name>"}

Migration stepsMigration steps

1. Make sure the data is available in Monium in the folder__<folder_ID> project.

2. Update your data delivery agent (Unified Agent, Fluent Bit 4.0) or use Otel Collector and configure delivery in OTel format.

3. Specify a new endpoint: ingest.monium.yandex.cloud:443. Without this, logs will still be delivered via Cloud Logging and billed accordingly.

4. Make sure logs are delivered to Monium directly, not via Cloud Logging.

   To check this, view service usage details by products in Yandex Cloud Billing. After migration, you should see usage details for logs in Monium. Cloud Logging usage should reduce or disappear.

   After migration, logs will be billed according to the Monium pricing and all platform features will become available.

5. Optionally, rename the projects, clusters, and services. You can leave the current structure: folder__<folder_ID> → default → log group name or provide your own naming. For more information, see Types of telemetry and general concepts.

Configuring your agent for OTel deliveryConfiguring your agent for OTel delivery

Unified AgentUnified Agent

1. Replace the output section in the configuration file.

   Previously:

   channel:
     output:
       plugin: yc_logs
       config:
         url: "ingester.logging.yandexcloud.net:443"
         log_group_id: "<log_group_ID>"
         folder_id: "<folder_ID>"
         iam:
           cloud_meta:
   

   Now:

   channel:
     output:
       plugin: otel_logs
       config:
         url: "ingest.monium.yandex.cloud:443"
         project: folder__<folder_ID>
         service: <service_name>
         iam:
           cloud_meta:
   

   The project property can be any: you can create your own projects in Monium. In the service property, specify the log group name to save the data structure.

2. To specify a cluster, add the cluster: <cluster_name> property. The default value is default.

Fluent BitFluent Bit

You can continue using Fluent Bit or configure delivery via OTel Collector.

1. Make sure that you have installed Fluent Bit version 4.0 or higher:

   apt show fluent-bit
   

2. Make sure that the configuration file is in YAML format. Support for the classic INI format will be discontinued at the end of 2026.

3. Replace the outputs section.

   Previously (yc-logging plugin):

   pipeline:
     outputs:
       - name: yc-logging
         ...
   

   Now (opentelemetry plugin):

   pipeline:
     outputs:
       - name: opentelemetry
         host: ingest.monium.yandex.cloud
         port: 443
         logs_uri: /otlp/v1/logs
         tls: on
         tls.verify: off
         header:
           - Authorization Api-Key ${API_KEY}
           - x-monium-project folder__<folder_ID>
   

   You can provide an IAM token instead of an API key: Authorization Bearer ${IAM_TOKEN}.

4. If the input plugin does not use OpenTelemetry or the service property is not set in messages, add the opentelemetry_envelope processor with these resource attributes:

   pipeline:
     inputs:
       - name: <input_plugin>
         processors:
           logs:
             - name: opentelemetry_envelope
             - name: content_modifier
               context: otel_resource_attributes
               action: upsert
               key: service.name
               value: <log_group_name>
             - name: content_modifier
               context: otel_resource_attributes
               action: upsert
               key: cluster
               value: default
   

   In the service.name property, specify the log group name to save the data structure. The cluster property is optional. The default value is default.

Reading logs via APIReading logs via API

Log reading via the Cloud Logging API will be supported until March 1, 2027 if you preserve the folder__<folder_ID> → default → log group name structure. The data is available within the storage period of 31 days.

Data reading via the Monium API and its documentation will become available in July 2026. Make sure to migrate read requests to the new API before the old API support is discontinued.