Yandex Managed Service for Prometheus® overview
Yandex Managed Service for Prometheus® is a monitoring system compatible with Prometheus. You can use it to collect, store, and read metrics from your containers, applications, and infrastructure. The system uses the Prometheus data model and the PromQL query language. This allows you to work with dashboards existing in Grafana.
Prometheus provides multiple mechanisms for collecting metrics, including libraries for popular programming languages and support for exporting metrics from third-party systems, like databases or message queues. Yandex Managed Service for Prometheus® allows you to use best practices of the Prometheus open source community, while ensuring high scalability, availability, and safety with no need to deploy Prometheus clusters and manage the internal monitoring infrastructure on your own. To get started with Yandex Managed Service for Prometheus®, just install agents that support the metric Remote Write protocol.
Yandex Managed Service for Prometheus® is based on the system that Yandex uses to monitor internal services. The system automatically scales metric writes, storage, and reads depending on the workload. High availability is ensured thanks to replication of the monitoring data in two availability zones.
Getting started
To start working with Yandex Managed Service for Prometheus® in the current folder, you need to create a workspace. To do this:
- Open the Yandex Monitoring home page.
- In the left-hand panel, select Prometheus.
- Click Create a workspace.
- On the page that opens, you will see links to the endpoints to be used for the current folder.
To enable metric writes and reads in Prometheus format, follow the corresponding guides.
Current features
Note
The system functionality will be enhanced in upcoming releases.
| Feature | Prometheus | Yandex Managed Service for Prometheus® |
|---|---|---|
| Collecting metrics | Scrape, Pushgateway, Remote Write | Metric writes via the Remote Write protocol are supported. To deliver metrics to Yandex Managed Service for Prometheus®, you can use any compatible metric collection agent, including Prometheus itself. |
| Long-term metric storage | Not intended for long-term metric storage. Third-party solutions are used for that. | Long-term metric storage is supported. If decimation is used, metrics can be stored for an unlimited amount of time. |
| Reading metrics | Data and metadata reads via the HTTP API are supported. | Data and metadata reads via the HTTP API are supported with some restrictions. |
| Visualization | Expression browser, Grafana | Prometheus data source is supported. |
| Aggregation | Aggregation via recording rules is supported. | Existing recording rules (recording rules) in YAML format are supported. To upload and manage the files, use the Monitoring UI and API. |
| Alerting | Aggregation via alerting rules is supported. | Existing alerting rules (alerting rules) in YAML format are supported. To upload and manage the files, use the Monitoring UI and API. |
| Integrations | Client libraries and exporters. | Existing libraries and exporters can be used. |
Note
Alerting rules are at the Technical Preview stage. To access the feature, contact support.
Current limitations
- The
NaNvalue is not supported and is treated as a missing point. - The
+Inf/-Infvalues may be processed incorrectly. - For alerting rules (
alerting rules), the only supported channels are email and Telegram. Dynamic routing is not supported. staleness markers,exemplars, andnative histogramsare not supported.
Quotas and limits
Yandex Managed Service for Prometheus® has the following limits:
- Quotas are organizational restrictions that can be changed by technical support.
- Limits are technical limitations due to Yandex Cloud architectural features. You cannot change the limits.
If you need more resources, contact support at cloud@support.yandex.ru and tell us which quotas you want increased and by how much.
Quotas per endpoint
| Type of limit | Value |
|---|---|
| Maximum data write speed in Remote Write format | 1,000 requests/s and 80 MB/s |
| Number of metrics per write request | 10,000 |
| Number of Remote Read API read requests per second | 200 |
| Number of HTTP API read requests per second | 200 |
| Number of unique metrics | 20,000,000 |
| Maximum retention period for expired metrics 1 | 60 days |
1 A metric expires and is removed if not getting new values for 60 days. Metrics that keep getting new values are stored indefinitely.
Here is what you can do in the Prometheus > Workspace > General information tab:
- View the number of written metrics.
- Go to the page with service dashboards and view the number of requests, errors, and HTTP status codes per second for various endpoints.
Limits per endpoint
| Type of limit | Value |
|---|---|
| Number of unique labels per metric | 29 |
© 2024 Linux Foundation. All rights reserved. The Linux Foundation owns and uses registered trademarks. For a list of Linux Foundation trademarks, see Trademark Usage.