mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-15 16:30:55 +01:00
d32a6359b0
* vmselect/promql: enable search.maxPointsPerTimeSeriesSubquery for sub-queries * vmselect/promql: cleanup * vmselect/promql: rename config flag * vmselect/promql: add tests * vmselect/promql: use test object instead of log * vmselect/promql: fix posible panic is subquery has more points. add description * vmselect/promql: update tests descriptions * vmselect/promql: update doInternal validation * vmselect/promql: fix linter * vmselect/promql: fix linter * vmselect/promql: update documentation and release notes * wip - Properly apply -search.maxPointsSubqueryPerTimeseries limit to subqueries. Previously the -search.maxPointsPerTimeseries limit was unexpectedly applied to subqueries if it was smaller than the -search.maxPointsSubqueryPerTimeseries . - Clarify docs for -search.maxPointsSubqueryPerTimeseries command-line flag . - Document -search.maxPointsPerTimeseries and -search.maxPointsSubqueryPerTimeseries flags at https://docs.victoriametrics.com/#resource-usage-limits . - Update docs/CHANGELOG.md . Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2922 Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com> |
||
---|---|---|
.. | ||
error_response.qtpl | ||
error_response.qtpl.go | ||
export.qtpl | ||
export.qtpl.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 | ||
tsdb_status_response.qtpl | ||
tsdb_status_response.qtpl.go | ||
util.qtpl | ||
util.qtpl.go |