Fork Frontend persistence to history service Rest API (PoC for Elastic)

XMLWordPrintable

    • Type: New Feature Request
    • Resolution: Duplicate
    • Priority: Trivial
    • 4.0 (plan)
    • Affects Version/s: 3.4.0alpha1
    • Component/s: API (A), Frontend (F)
    • None
    • Sprint 9, Sprint 10, Sprint 11, Sprint 12, Sprint 13, Sprint 14, Sprint 15, Sprint 16, Sprint 17, Sprint 18

      As a next step after ZBXNEXT-3877 is implemented:

      The front-end should be updated for using the REST api for retrieving history data instead of accessing the data using a direct connection to the underlying storage system. Decoupling the front-end from the need of a direct connection to the persistent storage, will make it completely agnostic about the storage mechanism, allowing a lot of different storage back-ends to be implemented, without worrying to modify the front-end at all.

        1. ZBXNEXT-3661.xls
          53 kB
          Oleg Egorov

            Assignee:
            Unassigned
            Reporter:
            Rostislav Palivoda (Inactive)
            Team C
            Votes:
            2 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: