As we know, the TimescaleDB feature is designed for databases and high-volume, professional environments. In these environments, not using a proxy is impractical and incurs high costs for the main server. However, even in the latest versions, Zabbix proxy does not support this feature, and it is very difficult to choose between TimescaleDB and the proxy!!! I hope a solution for this issue will be found soon.
As we know, the TimescaleDB feature is designed for databases and high-volume, professional environments. In these environments, not using a proxy is impractical and incurs high costs for the main server. However, even in the latest versions, Zabbix proxy does not support this feature, and it is very difficult to choose between TimescaleDB and the proxy!!! I hope a solution for this issue will be found soon.
Thanks for sharing! 👍🏻
Thanks Dmitry, what would be the procedure to configure the timescaledb postgres in Docker?
Pull the timescale container and then set the configuration with either environment vars or mapping config files from the host to the container
Something in comments:)
As we know, the TimescaleDB feature is designed for databases and high-volume, professional environments. In these environments, not using a proxy is impractical and incurs high costs for the main server. However, even in the latest versions, Zabbix proxy does not support this feature, and it is very difficult to choose between TimescaleDB and the proxy!!! I hope a solution for this issue will be found soon.
Cannot you just use PG + TimescaleDB on the main Zabbix server and simple PG on the Proxy servers?
@@DanielMoscalu ?
As we know, the TimescaleDB feature is designed for databases and high-volume, professional environments. In these environments, not using a proxy is impractical and incurs high costs for the main server. However, even in the latest versions, Zabbix proxy does not support this feature, and it is very difficult to choose between TimescaleDB and the proxy!!! I hope a solution for this issue will be found soon.