[ZBXNEXT-5013] TimescaleDB - further improvements Created: 2019 Feb 07 Updated: 2019 Mar 26 Resolved: 2019 Mar 04 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Server (S) |
Affects Version/s: | 4.2.0beta1, 4.2 (plan) |
Fix Version/s: | 4.2.0beta2, 4.2 (plan) |
Type: | Change Request | Priority: | Trivial |
Reporter: | Alex Kalimulin | Assignee: | Alex Kalimulin |
Resolution: | Fixed | Votes: | 5 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||||||
Team: | Team A | ||||||||
Sprint: | Sprint 49 (Feb 2019), Sprint 50 (Mar 2019) | ||||||||
Story Points: | 1.5 |
Description |
TimescaleDB changes versions and concepts very fast so Zabbix TimescaleDB support should catch up on the following:
|
Comments |
Comment by Jan Ostrochovsky [ 2019 Mar 15 ] |
Hello guys, what is current state of this initiative? Despite removed adaptive chunking, I still see TimescaleDB as being positive addition to ZABBIX, but interested in how you see that, if you see any obstacles . Thanks. Jano |
Comment by Alex Kalimulin [ 2019 Mar 15 ] |
ostry, the status of the ticket is "CLOSED", resolution "Fixed". We don't see any obstacles at the moment but if you have any experience to share will be glad to hear. |