-
New Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
There are number of drawbacks of current implementation of Zabbix API:
- code duplication (C, PHP)
- poor performance especially for template related operations
- lack of bulk operations and in-memory cache
- API code is too tied to front-end code (no clear separation)
- API is not available without Zabbix front-end
It's proposed to move API to Zabbix Server side.