Terms of Use of Yandex Cloud Monium

This document contains specific Terms of Use of Yandex Cloud Monium (“the Service”) and is an integral part of Yandex.Cloud Customer Agreement (”Agreement”) and Service Terms set forth at https://yandex.com/legal/cloud_service_terms. Capitalized terms used herein but not defined herein shall have the meanings set forth in Agreement and Linked Documents.

1. Functional Features of the Service

1.1. The Service enables the Customer to use following capabilities: Yandex Monium Metrics, Yandex Monium Logs, Yandex Monium Traces. The Customer is provided with the following options as part of the Service:

1.1.1. The Yandex Monium Metrics («Yandex Monium Metrics») functionality provides the Customer with the following capabilities:

i. Collecting, storing, and exporting data on Platform resources used, as well as on Customer-owned resources;

ii. Creating graphical visualizations containing up-to-date data on Platform resources used and Customer-owned resources;

iii. Configuring and combining multiple graphical visualizations into unified dashboards;

iv. Setting up checks (Alerts) based on data from used Platform resources and Customer-owned resources;

v. Configuring notification channels and escalation policies to receive alerts about triggered checks (Alerts);

vi. Sending notifications about triggered checks (Alerts) to recipients specified in the Customer’s notification channels and escalation policies. Notifications may be delivered via email, SMS, push notifications in the Yandex Cloud mobile application, messages in the Telegram messenger, or phone calls.

1.1.2. The Yandex Monium Logs functionality provides the Customer with the following capabilities:

i. Adding and reading logs of the Customer’s software and Services using the OpenTelemetry protocol directly from the Customer’s applications and/or via delivery agents;

ii. Creating, storing, and reading log entries.

1.1.3. The Yandex Monium Traces functionality provides the Customer with the following capabilities:

i. Collecting, receiving, storing, indexing, analyzing, and visualizing distributed traces and their constituent execution spans (Spans), generated by the Customer’s software and/or Platform resources;

ii. Receiving telemetry via the OpenTelemetry protocol directly from the Customer’s applications and/or via collectors;

iii. Accepting Spans and Traces from the Customer’s applications running both on Platform resources and on Customer-owned resources;

iv. Generating trace views, duration diagrams, Service Maps, and other graphical visualizations to analyze performance and dependencies between functionalities;

v. Searching, filtering, and aggregating by Span/Trace attributes.

1.1.4. other functional features of the Service, which Yandex makes available to Customer. The functional features of the Service are fully described in the technical specifications and Service Documentation available on the Site.

1.2. Service Level is determined for the Service in accordance with SLA.

2. Pricing

2.1. The use of the Service is chargeable.

2.2. Service Fee for the Service is determined as per Service Rates and billing units specified on Site. Yandex may change Service Rates as prescribed by Agreement.

2.3. Service Fee for the Yandex Monium Metrics depends on the number of operations performed and the volume of data written and read.

2.4. Service Fee for the Yandex Monium Logs depends on the volume of log entries created.

2.5. Service Fee for the Yandex Monium Traces depends on the volume of received and processed trace data, as well as on the volume and duration of data storage.

2.6. Yandex may from time to time provide Customer with additional functional features of the Service for an additional fee.

3. Limitations

3.1. The Service envisages a number of restrictions listed in the Quotas and Limits section of the Site.

4. Data processing

4.1. When using the Service, the Customer entrusts Yandex with the processing of personal data that may be present in the Service.

4.2. The Data Processing Addendum (posted on the Internet at the following addresses) applies to the relations of the Parties when using the Service: https://yandex.com/legal/cloud_dpa or https://yandex.com/legal/cloud_dpa_kz ), in the part that does not contradict these terms and conditions, as well as taking into account the functional features of the Service. In case of discrepancies between the Data Processing Addendum and these terms, these terms shall prevail.

4.3. The Customer warrants that it ensures presence and validity of the legal bases for processing end-users’ personal data that are required under applicable laws for processing by Yandex in the volume and within the timeframes set out in these terms.

4.4. The Customer undertakes to notify end-users about processing of their personal data under these terms in an appropriate manner.

4.5. The Customer shall handle Users’ requests related to the processing and protection of personal data. If requested by the Customer, Yandex will assist in responding to such requests where and to the extent possible, based on the functional features of the Service.

Definitions

Terms used in these Terms with a capital letter and not otherwise defined in the Offer or in the terms of use of other Services shall have the following meanings:

  • Graphical Visualization — up-to-date data regarding one or more Platform resources used by the Customer or Customer-owned resources, presented in the form of a chart or graph.
  • Customer-owned Resources — the Customer’s own software and hardware resources, such as software, applications, etc., not part of the Yandex Cloud Platform.
  • Alert — a named set of notification rules for deviations in data values, with configurable threshold values to determine such deviations.
  • Log Entry — the smallest indivisible unit of user information, which may include data about events and/or operations occurring in the Services or in the Customer’s software deployed on the Platform.
  • OpenTelemetry Protocol — a protocol for exchanging telemetry data (including Spans), used by the Service to receive data (e.g., via gRPC and/or HTTP).
  • Trace — a set of related Spans forming a tree (or graph) of a distributed operation, identified by a common trace_id.
  • Span — the smallest logical unit of trace data, describing a single operation execution interval (e.g., a remote service call or request processing), containing timestamps, attributes, events, and execution status.
  • Collector — a software component that receives telemetry from the Customer’s applications and forwards it to the Service according to sampling and routing policies.
  • Service Map — a visualization of dependencies and interactions between the Customer’s application services and components, based on trace data.

________________________________________

Web address: https://yandex.com/legal/cloud_terms_monium

Date of placement: 02.03.2026

Effective date: 02.03.2026