-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grafana API datasource health check returns 400 #208
Comments
Hi @eserte ! Can you share how you configure the data source in the grafana? If it is possible, can you share the picture of how you set up your cluster. It will help to understand where the problem is |
Hi @dmitryk-dk, grafana's datasource API returns the following for this datasource (obfuscated):
Probably this is the URL which is built for the health check: |
@dmitryk-dk : the fix does not work. Problem is probably the usage of (And reopening issues in github does not seem to be possible, at least for non-owners) |
HI @eserte! Could you please check the release v0.6.1, please? |
Thanks, v0.10.1 works fine. |
Sorry made changes in the both repositories and mention victorialogs-datasource release :) |
When using the grafana API datasource health check against a datasource using the victoriametrics-datasource plugin, e.g. using
/api/datasources/uid/abcdefghijklmn/health
then it fails with a 400 status and a JSON bodyThe datasource is configured with the URL
http://vmselect-aggregator-clusterip.vm-output.svc.cluster.local:8481/select/1234/prometheus
(note the multi-tenant setup) and otherwise works fine, only the above health check does not.If I understand the source code correctly, then the health check is done in this function https://github.com/VictoriaMetrics/victoriametrics-datasource/blob/main/pkg/plugin/datasource.go#L169
The
/-/healthy
part is just added to the configured URL, so the result would behttp://vmselect-aggregator-clusterip.vm-output.svc.cluster.local:8481/select/1234/prometheus/-/healthy
which does not work. It returns an error message containing... unsupported path requested: "/select/1234/prometheus/-/healthy"
and the http status is 400 which looks like it is propagated.The text was updated successfully, but these errors were encountered: