mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-15 08:23:34 +01:00
f5559c038c
This limit has little sense for these APIs, since:
- Thses APIs frequently result in scanning of all the time series on the given time range.
For example, if extra_filters={datacenter="some_dc"} .
- Users expect these APIs shouldn't hit the -search.maxUniqueTimeseries limit,
which is intended for limiting resource usage at /api/v1/query and /api/v1/query_range requests.
Also limit the concurrency for /api/v1/labels, /api/v1/label/.../values
and /api/v1/series requests in order to limit the maximum memory usage and CPU usage for these API.
This limit shouldn't affect typical use cases for these APIs:
- Grafana dashboard load when dashboard labels should be loaded
- Auto-suggestion list load when editing the query in Grafana or vmui
Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5055
|
||
|---|---|---|
| .. | ||
| error_response.qtpl | ||
| error_response.qtpl.go | ||
| expand-with-exprs.qtpl | ||
| expand-with-exprs.qtpl.go | ||
| export.qtpl | ||
| export.qtpl.go | ||
| federate_test.go | ||
| federate_timing_test.go | ||
| federate.qtpl | ||
| federate.qtpl.go | ||
| label_values_response.qtpl | ||
| label_values_response.qtpl.go | ||
| labels_response.qtpl | ||
| labels_response.qtpl.go | ||
| prometheus_test.go | ||
| prometheus.go | ||
| query_range_response.qtpl | ||
| query_range_response.qtpl.go | ||
| query_response.qtpl | ||
| query_response.qtpl.go | ||
| series_count_response.qtpl | ||
| series_count_response.qtpl.go | ||
| series_response.qtpl | ||
| series_response.qtpl.go | ||
| tenants_response.qtpl | ||
| tenants_response.qtpl.go | ||
| tsdb_status_response.qtpl | ||
| tsdb_status_response.qtpl.go | ||
| util.qtpl | ||
| util.qtpl.go | ||