use a remote RDBMS (e.g., Postgres) rather than just local SQLite

[clickonetwo]

For hardening purposes, it would be good to have multiple proxy instances running (both for load balancing and redundancy). But they should use a common database, rather than each using a separate local SQLite instance. This means it needs to be a remote relational database, such as Postgres or MySQL.

[thomasberglund]

Hello. This enhancement would also make visualizing of data via Grafana much easier. PostgreSQL and TimescaleDB seems like a great fit as data source for robust monitoring via Grafana. What do you think?

https://grafana.com/docs/grafana/latest/datasources/postgres/

TimescaleDB — A time-series database built as a PostgreSQL extension. When enabled, Grafana uses time_bucket in the $__timeGroup macro to display TimescaleDB specific aggregate functions in the query builder (only available in Grafana 5.3+).

https://github.com/timescale/timescaledb

[clickonetwo]

@thomasberglund It looks to me like TimescaleDB wants the date storage in Postgres to be in timestamp (with timezone) format. The current storage is a date string. Moving to a timestamp would mean that older data would not be usable or would have to be converted. Would this be a problem for you?

[thomasberglund]

@clickonetwo Understood. This would not be a problem. We already have data from "ulecs" since august, but there is no issue starting fresh once we get something like this working with Postgres and TimescaleDB, as a source for Grafana visualization. 🙂