You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of using the Postgres protocol, why not use the HTTP one instead since you're building a plugin anyway. HTTP is way more flexible, easier to setup and easier to add auth behind.
QuestDB version:
1
Grafana version:
1
Plugin version:
1
OS, in case of Docker specify Docker and the Host OS:
1
Full Name:
1
Affiliation:
1
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
Yes, I have
Additional context
No response
The text was updated successfully, but these errors were encountered:
The Clickhouse plugin supports HTTP. I won't use QuestDB until the Grafana plugins supports HTTP protocol instead of TCP. HTTP is much easier to set up and secure over the internet. Why did you add HTTP querying if you're not going to support it?
Yes, HTTP is much easier to work with, you can merge and split and route and authenticate requests all on a single port and with robust (ACME provided) encryption using a plethora of available reverse proxies. Using the Postgres wire format is just pain.
To reproduce
Instead of using the Postgres protocol, why not use the HTTP one instead since you're building a plugin anyway. HTTP is way more flexible, easier to setup and easier to add auth behind.
QuestDB version:
1
Grafana version:
1
Plugin version:
1
OS, in case of Docker specify Docker and the Host OS:
1
Full Name:
1
Affiliation:
1
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
Additional context
No response
The text was updated successfully, but these errors were encountered: