Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • 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.
Monium
  • Getting started
  • Overview
    • Overview
    • OpenTelemetry SDK
    • OTel Collector
  • Access management
  • Pricing policy
  • Terraform reference
  • Release notes

In this article:

  • Data transfer parameters
  • Data transfer agents
  1. Data collection
  2. Overview

Collecting telemetry

Written by
Yandex Cloud
Updated at February 24, 2026
  • Data transfer parameters
  • Data transfer agents

Data transfer parametersData transfer parameters

To transmit telemetry to Monium:

  1. Set up telemetry collection from your application in OpenTelemetry format.

    You can send telemetry directly from the application or via an agent.

  2. Create a service account.

  3. Create an API key for the service account with the required scopes:

    • yc.monitoring.manage: Writing data.
    • yc.monium.telemetry.write: Writing all telemetry types.
    • yc.monium.metrics.write: Writing metrics.
    • yc.monium.logs.write: Writing logs.
    • yc.monium.traces.write: Writing traces.
  4. Specify data transfer settings:

    • Endpoint: ingest.monium.yandex.cloud:443.
    • Protocol: gRPC or HTTP.
  5. In Monium, telemetry follows this hierarchy: project → cluster → service. Data is stored in shards in service-cluster pairs.

    To distribute data, specify:

    • Project: Provided as the x-monium-project header parameter. This may be a folder__<folder_ID> or a cloud__<cloud_ID>.
    • Cluster: Provided in OTEL_RESOURCE_ATTRIBUTES with the cluster or deployment.name key name. This is optional. If a cluster is not specified, data will go to the default cluster.
    • Service: Provided in OTEL_RESOURCE_ATTRIBUTES with the service or service.name key name.

    Monium stores data in shards with the project, cluster, and service keys. The shard key is selected based on a priority table, with priority decreasing from left to right.

    header resource attribute resource attribute constant
    x-monium-project — — —
    x-monium-cluster cluster deployment.name default
    x-monium-service service service.name default

Data transfer agentsData transfer agents

With Monium, you can manage telemetry from Yandex Cloud resources, other clouds, or applications in your infrastructure.

Transfer of Yandex Cloud data is set up when you create or update a resource.

To set up data transfer from applications, do one or both of the following:

  • Connect the OpenTelemetry SDK and set up OTLP export.
  • Use automation tools, i.e., agents or libraries that automatically collect telemetry from popular frameworks and libraries without modifying the code.

You can transfer data to Monium directly from the OpenTelemetry SDK or use an OTLP-compatible agent.

The agent is installed next to the application on a server, VM, or in a container and set up to receive telemetry and send it to Monium. If the application is configured to send data in a format other than OTLP, you will need an intermediate agent for OTLP conversion.

Learn more about setting up agents:

  • Unified Agent: Agent by Yandex.
  • OTel Collector: OpenTelemetry ecosystem agent.
  • Fluent Bit: Agent to use for logs.

Was the article helpful?

Previous
Overview
Next
OpenTelemetry SDK
© 2026 Direct Cursus Technology L.L.C.