Details
-
Type:
New Feature Request
-
Status: Closed
-
Priority:
Trivial
-
Resolution: Duplicate
-
Affects Version/s: 3.4.0alpha1
-
Fix Version/s: 4.0 (plan)
-
Component/s: API (A), Frontend (F)
-
Labels:None
-
Team:Team C
-
Sprint:Sprint 9, Sprint 10, Sprint 11, Sprint 12, Sprint 13, Sprint 14, Sprint 15, Sprint 16, Sprint 17, Sprint 18
Description
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.
Attachments
Issue Links
- causes
-
ZBX-13517 Undefined index in history manager
-
- Closed
-
- depends on
-
ZBXNEXT-4002 Implement REST API history service calls in server (PoC for Elastic)
-
- Closed
-
- part of
-
ZBXNEXT-3877 Implement history service calls in server (PoC for Generic Rest API)
-
- Closed
-