[Yandex Cloud documentation](../../index.md) > [Monium](../index.md) > Logs > Migrating from Monium.Logs

# Migrating from Monium.Logs to Monium

{% note warning %}

Monium.Logs will be shut down in Q2 2027. Use the [Monium](../index.md) Observability platform instead of it.

{% endnote %}

## Monium.Logs and Monium comparison {#comparison}

#|
|| | **Monium.Logs** | **Monium** ||
|| **Write** | $0.2094299665 (GB per month) | $0.036065568 (GB per month) ||
|| **Storage** | You are billed for | You are not billed for, [TTL](../concepts/common-ttl.md#ttl-logs): 31 days ||
|| **Reading and analytics** | Basic log search | Aggregations, unified query language for logs, metrics, and traces ||
|| **Migration** | — | Changing format (OTEL) and endpoint ||
|#

All prices are shown in the [Monium.Logs](../../logging/pricing.md#prices) and [Monium pricing policies](../pricing.md#prices).

## Testing Monium without migration {#preview}

Logs from Monium.Logs are already available in Monium. Open them in the [management console](https://console.yandex.cloud) in one of the following ways: 

* When viewing logs in Monium.Logs, 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 steps {#migration-steps}

1. [Make sure](#preview) the data is available in Monium in the `folder__<folder_ID>` project.

1. Update your data delivery agent (Unified Agent, Fluent Bit 4.0) or use [Otel Collector](../collector/opentelemetry.md) and [configure delivery in OTel format](#agent-setup).

1. Specify a new endpoint: `ingest.monium.yandex.cloud:443`. Without this, logs will still be delivered via Monium.Logs and billed accordingly.

1. Make sure logs are delivered to Monium directly, not via Monium.Logs.

   To check this, [view service usage details](../../billing/operations/check-charges.md#products) by products in Yandex Cloud Billing. After migration, you should see usage details for logs in Monium. Monium.Logs usage should reduce or disappear.

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

1. 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 [Data model in Monium.Metrics](../concepts/data-model.md).

## Configuring your agent for OTel delivery {#agent-setup}

### Unified Agent {#unified-agent}

1. Replace the `output` section in the configuration file.

   **Previously:**

   ```yaml
   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:**

   ```yaml
   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](../collector/project.md) in Monium. In the `service` property, specify the log group name to save the data structure.

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

### Fluent Bit {#fluent-bit}

You can continue using Fluent Bit or configure delivery via [OTel Collector](../collector/opentelemetry.md).

1. Make sure that you have installed [Fluent Bit](https://fluentbit.io/) version 4.0 or higher:

   ```bash
   apt show fluent-bit
   ```

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

1. Replace the `outputs` section.

   **Previously** (`yc-logging` plugin):

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

   **Now** (`opentelemetry` plugin):

   ```yaml
   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}`.

1. 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:

   ```yaml
   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 API {#api-reading}

[Log reading via the Monium.Logs API](../../logging/api-ref/grpc/LogReading/read.md) 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.