Skip to content
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

Use HTTP protocol instead of Postgres #77

Open
1 task done
nlnw opened this issue Apr 22, 2024 · 1 comment
Open
1 task done

Use HTTP protocol instead of Postgres #77

nlnw opened this issue Apr 22, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@nlnw
Copy link

nlnw commented Apr 22, 2024

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?

  • Yes, I have

Additional context

No response

@nlnw nlnw added the bug Something isn't working label Apr 22, 2024
@nlnw
Copy link
Author

nlnw commented Jun 13, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant