Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-4002

Implement REST API history service calls in server (PoC for Elastic)

XMLWordPrintable

    • Team A
    • Sprint 13, Sprint 14, Sprint 15, Sprint 16, Sprint 17, Sprint 18, Sprint 19, Sprint 20, Sprint 21, Sprint 22
    • 2

      Storing of historical data from server to Elastic search.

      In scope of Epic ZBXNEXT-3661, continues from ZBXNEXT-3877 , but we change REST API format to be compatible with Elastic.

      Pros:

      • users still able to create their own service that match Elasic API.
      • we do not introduce new dependencies to Zabbix and user free to choose service implementation language.
      • our support is limited to API.

      Cons:

      Scope:
      1. It is required to implement initial elastic schema creation script that will describe all documents and document fields required for Zabbix to work.
      2. Change API to match Elastic.

      Out of scope, future improvements:
      1. allow configuration of data storage per value type
      2. allow callbacks to enrich the data with Item name, ID and Host name, ID.

        1. 1510662545550.jpg
          243 kB
          Natalja Romancaka

            Unassigned Unassigned
            palivoda Rostislav Palivoda
            Team A
            Votes:
            5 Vote for this issue
            Watchers:
            22 Start watching this issue

              Created:
              Updated:
              Resolved: