Is your feature request related to a problem? Please describe
No response
Describe the solution you'd like
VictoriaMetrics provides a multitenant endpoint under http://vmselect:8481/select/multitenant/<suffix> (see VMetrics Docs, discussed in Issue #1434. It would be great to have such an endpoint supported for VictoriaLogs aswell.
Describe alternatives you've considered
Following the documentation, querying logs of different tenants in VictoriaLogs is currently only supported by supplying HTTP-Headers specifying the AccountID and ProjectID of the tenant to query logs of. In Grafana for example, this means that one datasource per tenant is required. With the /multitenant endpoint of VictoriaMetrics, only one datasource is required, making queries across different tenants much easier.
Additional information
Querying the multitenant endpoint in vlselect returns the following response:
curl http://vlselect:9471/select/multitenant
remoteAddr: "127.0.0.1:33636"; requestURI: /select/multitenant; unsupported path requested: "/select/multitenant"
Is your feature request related to a problem? Please describe
No response
Describe the solution you'd like
VictoriaMetrics provides a multitenant endpoint under
http://vmselect:8481/select/multitenant/<suffix>(see VMetrics Docs, discussed in Issue #1434. It would be great to have such an endpoint supported for VictoriaLogs aswell.Describe alternatives you've considered
Following the documentation, querying logs of different tenants in VictoriaLogs is currently only supported by supplying HTTP-Headers specifying the AccountID and ProjectID of the tenant to query logs of. In Grafana for example, this means that one datasource per tenant is required. With the /multitenant endpoint of VictoriaMetrics, only one datasource is required, making queries across different tenants much easier.
Additional information
Querying the multitenant endpoint in vlselect returns the following response: