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.

Sign up for GitHub

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

Jump to bottom

Switch grafana to use SQLite instead of using timescaledb instance #338

Closed
paulfantom opened this issue May 9, 2022 · 2 comments · Fixed by #404
Closed

Switch grafana to use SQLite instead of using timescaledb instance #338

paulfantom opened this issue May 9, 2022 · 2 comments · Fixed by #404
Assignees
@paulfantom
Labels
enhancement Improvement of an existing feature tech-debt
Milestone
0.11.0

Comments

@paulfantom
Copy link
Contributor

What is missing?

We are shipping our own, custom database instance for grafana. This seems to be unnecessary and just adding resource requirements. Instead I would propose to revert to using native grafana sqlite implementation. Users should still be able to connect grafana to postgresql if they wish to.

Why do we need it?

Additional components increase security risk as well as potential tech-debt.

Anything else we need to know?:
@paulfantom paulfantom added feature New features tech-debt enhancement Improvement of an existing feature and removed feature New features labels May 9, 2022
@paulfantom
Copy link
Contributor Author

Relates to #371

@paulfantom paulfantom added this to the 0.11.0 milestone May 25, 2022
@paulfantom paulfantom mentioned this issue May 30, 2022
Merged
5 tasks
@paulfantom paulfantom changed the title Consider switching grafana to use SQLite instead of provisioning separate postgresql instance Consider switching grafana to use SQLite instead of using timescaledb instance May 30, 2022
@paulfantom paulfantom self-assigned this May 31, 2022
@paulfantom paulfantom changed the title Consider switching grafana to use SQLite instead of using timescaledb instance Switch grafana to use SQLite instead of using timescaledb instance Jun 8, 2022
@Davincible
Copy link
Contributor

Davincible commented Jun 26, 2022 •
edited
Loading

@paulfantom could you elaborate a bit more on why you decided on this change? As I was a bit confused by it.

Additional components increase security risk as well as potential tech-debt.

If we are using a timescaledb instance anyways, for metrics and often also business services, why not use it for grafana as well? Extra components, security, and tech-debt seem like non-issues in that case, besides that it could potentially perform better.

@Davincible Davincible mentioned this issue Jun 27, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paulfantom paulfantom

Labels
enhancement Improvement of an existing feature tech-debt
Projects
None yet
Milestone
0.11.0
Development

Successfully merging a pull request may close this issue.

chart: Use SQLite for grafana instead of timescaledb paulfantom/tobs
2 participants
@paulfantom @Davincible