Split history TimescaleDB chunk retention policy for numerical and textual data types

XMLWordPrintable

    • Type: New Feature Request
    • Resolution: Unresolved
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      Currently all history hypertables have the same retention policy setting in the Housekeeper settings.
      Let's say you want to keep less textual data as it takes up more space than numerical data, but you want to keep the same amount of numerical history data. Currently If you lower the history retention period, it will apply the settings for all the history hypertables.

      This feature request suggests to split the history tables retention policy into 2 parts, one configurable retention policy would be for numerical data (history, and one for textual data.

            Assignee:
            Zabbix Development Team
            Reporter:
            Tomass Janis Bross
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: