[Yandex Cloud documentation](../../index.md) > [Monium](../index.md) > Concepts > Quotas and limits

# Monium quotas and limits

There are restrictions (quotas and limits) on a number of resources in Monium.

* [_Quotas_](https://console.yandex.cloud/cloud?section=quotas) are organizational constraints that can be changed by contacting technical support.
* _Limits_ are technical constraints of the Yandex Cloud architecture. You cannot change the limits.

## Viewing current quotas {#view-quotas}

{% list tabs group=instructions %}

- Monium UI {#console}
  
  1. On the [Monium](https://monium.yandex.cloud) home page, select **Quotas** on the left.
  1. Select the project in the top left or leave the current one.
  1. On the **Project quotas** tab, view the quota values ​​for resource groups.
  1. To view quotas for individual shards, go to the **Distribution by shards** tab on the **Quotas** page.
  1. For each shard, it gives the following values:
     * **Used**: Shard's current resource consumption.
     * **Limit**: Shard's maximum quota.
     * **Utilization**: Share of used quota (consumption to limit ratio). Shows how close current consumption is to the quota.

{% endlist %}

## Changing quotas {#change-quotas}

{% list tabs group=instructions %}

- Monium UI {#console}
  
  1. Make sure your account has the [monium.admin](../security/index.md#monium-admin) or [monium.editor](../security/index.md#monium-editor) role.
  1. On the [Monium](https://monium.yandex.cloud) home page, select **Quotas** on the left.
  1. Select the project in the top left or leave the current one.
  1. On the **Project quotas** tab, in the quota group, click ![image](../../_assets/console-icons/pencil.svg) **Change quota amount**.
  1. In the window that opens, enter new values for the group's quotas.
  1. Click **Create request**.

{% endlist %}

You can increase and decrease quotas.

A quota increase is confirmed automatically but only up to a certain limit. If a higher quota is required, the system will prompt you to contact [support](https://center.yandex.cloud/support) for further approval.

Reducing the quota helps you limit unexpected consumption spikes. For example, after a release, the application started to generate too many logs. In which case you can first reduce the quota and then proceed to investigate the cause, roll back the release, or make a fix. This will help you manage your expenses.

## Resources subject to quotas {#quota-resources}

* **Metrics**:
  * `Metrics Write`: Speed of writing points to shard metrics, in points per second. Once the quota is exhausted, the service will randomly discard points for stored metrics. The charts may start having gaps.
  * `Stored Metrics`: Number of unique metrics (time series). Once the quota is exhausted, new metrics will not be saved. Data will continue to be written to existing metrics.
* **Alerts**:
  * `Alerts Count`: Number of alerts and sub-alerts in the project. Once the quota is exhausted, you will not be able to create new alerts and sub-alerts.
* **Logs**:
  * `Logs Write`: Stream of logs to write, [mebibytes](https://en.wikipedia.org/wiki/Byte#Multiple-byte_units) per second. Once the quota is exhausted, the service will begin randomly discarding incoming logs.
* **Traces**:
  * `Spans Write`: Stream of spans to write, mebibytes per second. Once the quota is exhausted, the service will begin randomly discarding incoming spans. Because of this, some traces may not be fully collected.

## Quotas and limits {#limits-quotas}

### Quotas {#default-quotas}

The table shows the default quota values ​​set for a new project in Monium.

#|
|| Type of limit | Value ||
|| Speed ​​of writing points to shard metrics, `Metrics Write` | 20 million/sec ||
|| Number of unique metrics (time series), `Stored Metrics` | 200 million ||
|| Number of alerts per project, `Alerts Count` | 30,000 ||
|| Stream of logs to write, `Logs Write` | 150 MiB/s ||
|| Stream of spans to write, `Spans Write` | 150 MiB/s ||
|#

### Metric and alert limits {#limits-metrics-alerts}

**General limits**

Type of limit | Value
----- | -----
Number of labels per metric<br/>(including required ones) | 16
Number of values per label | 1,000

**API limits**

Type of limit | Value
----- | -----
Maximum number of metrics returned in the data export API request | 500
Maximum number of metrics sent in the data import API request | 10,000
Minimum number of samples returned in the data export API request | 10
Maximum number of samples returned in the data export API request | 10,000
Minimum time interval for exporting metrics | 1 second

**Alerting limits**

Type of limit | Value
----- | -----
Number of metrics per alert | 1 000
Number of SMS per number per day | 100

### Log limits {#limits-logs}

Type of limit | Value
--------------- | --------
Maximum size of one log batch | 8 MB
Maximum log start time in the past (`time_unix_nano`) | 24 hours ago
Maximum log time in the future (`time_unix_nano`) | 5 minutes ahead
Maximum [label](data-model.md#label) name length | 64 bytes
Maximum label value length | 256 bytes
Maximum [metadata](data-model.md#meta) name length | 400 bytes
Maximum metadata value length | 1 MB

{% note info %}

Allowed log batch size is up to 16 MB, but receipt this big is not guaranteed.

{% endnote %}

### Trace limits {#limits-traces}

**Retention limits**

Type of limit | Value
--------------- | --------
Data retention period for all spans | 4 days

**Write limits**

Type of limit | Value
--------------- | --------
Maximum size of a span batch | 4 MB
Maximum span start time in the past (`startTimeUnixNano`) | 24 hours ago
Maximum span end time in the future (`endTimeUnixNano`) | 1 hour from now
Maximum span `name` length | 2,048 characters
Maximum number of span `attributes` | 512
Maximum attribute name length | 256 characters
Maximum attribute value length | 2,097,152 characters
Maximum `events` per span | 256

**Read limits**

Type of limit | Value
--------------- | --------
Maximum number of spans displayed in the trace viewing interface | 100,000

For larger traces, split them into multiple traces and link them using [span links](https://opentelemetry.io/docs/concepts/signals/traces/#span-links).