-
Notifications
You must be signed in to change notification settings - Fork 0
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
Plugin health check failed #108
Comments
Hi @MichaelCarrik , thanks for raising the issue! Typically when the plugin health check fails, this means there is a problem with connection details - have you put all the necessary host/port/user/pass values (all are empty by default) and selected "disable" for TLS if working with localhost instance? |
Hello, I came across the same issue. Configurations looks ok, tls is disabled. But it does not work. Trying to detect the reason. UPD: I attached to grafana container's shell, questdb is accessible with RESTAPI. Credentials from docker compose are ok. How does health checker work? I will try to check Postgres Wire Protocol UPD2: Grafana visualization is failed with error: Finally I got answer - It turns out questdb has different credentials dependant of used protocol. I used ones from RESTAPI. |
I'm having the same issue, and after couple of time "learn" the new environment (I'm very new to Docker, and QuestDB also), so here is some information: https://github.com/questdb/grafana-questdb-datasource/?tab=readme-ov-file#configuration `To configure a readonly user, follow these steps: Open Source version Because I use Windows, so I need to go to this location to modify the config file. for other system, follow these instructions https://questdb.com/docs/concept/root-directory-structure/ |
To reproduce
Plugin health check failed
QuestDB version:
7.4.2
Grafana version:
11.1 、10.4.5、9.5.20
Plugin version:
0.13
OS, in case of Docker specify Docker and the Host OS:
centos7
Full Name:
yingwei
Affiliation:
oss
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
Additional context
Plugin health check failed
The text was updated successfully, but these errors were encountered: