Aliaksandr Valialkin

@justinrush , @zekker6 , @hagen1778 , please see the follow-up commit 65ce4e30ab380177dfde070a7ca19862636c13d5

@AndrewChubatiuk , @hagen1778 , please see the follow-up commit 74affa3aecd769ef94cc4f50774c1759518d8619

The main reason for the lack of vmstorage API at VictoriaMetrics single-node is that we haven't decided how to handle requests from vmselect for different tenants. Single-node VictoriaMetrics doesn't support...

Let's prioritize this feature because it solves the following important cases: - It simplifies the migration path from single-node to cluster version of VictoriaMetrics. When you reach single-node vertical scalability...

@hagen1778 , @AndrewChubatiuk , please see the follow-up commit db557b86ee483a6dea726f6021afe1755737a865

As for traces take a look at [VictoriaTraces](https://github.com/VictoriaMetrics/VictoriaTraces).

FYI, VictoriaLogs provides the [`/select/tenant_ids` endpoint](https://docs.victoriametrics.com/victorialogs/querying/#querying-tenants) starting from [v1.38.0 release](https://docs.victoriametrics.com/victoriametrics/changelog/), so this endpoint can be used by Grafana plugin for VictoriaLogs. Note that this endpoint expects empty `AccountID` request header...

See also similar feature request for [built-in web UI for VictoriaLogs](https://docs.victoriametrics.com/victorialogs/querying/#web-ui) - https://github.com/VictoriaMetrics/VictoriaLogs/issues/821 .