Aliaksandr Valialkin

VictoriaMetrics doesn't use `-search.maxUniqueTimeseries` command-line flag value when processing requests to `/api/v1/labels` and `/api/v1/label/.../values`, starting from [v1.97.0](https://docs.victoriametrics.com/CHANGELOG.html). Closing the issue as resolved.

FY, the [v1.97.3 LTS release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.97.3) takes into account `-search.maxUniqueTimeseries` when requesting `/api/v1/labels` and `/api/v1/label/.../values` as it was in `v1.96.0`.

FYI, commits fab02faa3f7c80d76bb28dc118fc7398abcfe544 and 0b7a23a91d5f29535c3c485f0c1d92f87ae91fef add `-search.ignoreExtraFiltersAtLabelsAPI` command-line flag, which can be set in order to ignore `match[]`, `extra_filters[]` and `extra_label` query args at `/api/v1/labels` and `/api/v1/label/.../values`. This allows reducing...

There was a bug in `-search.ignoreExtraFiltersAtLabelsAPI` implementation, which broke requests to `/api/v1/series`. This bug has been fixed in the commit https://github.com/VictoriaMetrics/VictoriaMetrics/commit/271173294407937cae4452464348672ff5699ae5 .

FYI, VictoriaMetrics doesn't use `-search.maxUniqueTimeseries` and `-search.maxQueryDuration` command-line flag values for limiting the number of processed series and the duration of queries to [`/api/v1/labels`](https://docs.victoriametrics.com/url-examples/#apiv1labels) and [`/api/v1/label/.../values`](https://docs.victoriametrics.com/url-examples/#apiv1labelvalues) starting from [v1.99.0](https://docs.victoriametrics.com/changelog/). Instead,...

Additional information, which could be useful for users, who encounter slow queries to [`/api/v1/labels`](https://docs.victoriametrics.com/url-examples/#apiv1labels) and [`/api/v1/label_values`](https://docs.victoriametrics.com/url-examples/#apiv1labelvalues) when loading Grafana dashboards with the defined `Label values` [template variables](https://grafana.com/docs/grafana/latest/datasources/prometheus/template-variables/): **always** specify the...

FYI, the commits 2d31fd7855bf304175348b502059eaf7b606af95 and d1d2771bee6e4d8807322ec4ad77fb95cd4ade36 improve performance for `/api/v1/labels` and `/api/v1/label/.../values` calls when `match[]` filter contains metric name. For example, `/api/v1/label/instance/values?match[]=up` should be executed must faster now. These commits...

FYI, the performance of `/api/v1/labels` and `/api/v1/label/.../values` APIs has been improved significantly starting from [v1.100.0 release](https://docs.victoriametrics.com/changelog/) when the `match[]` filter contains metric name. For example, `/api/v1/label/instance/values?match[]=up` now works much faster...

FYI, the fix for this issue has been included in [v1.93.13 LTS release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.13).

FYI, the fix for this issue has been included also in [v1.97.3 LTS release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.97.3).