API service standalone?

[angelhc]

Hi all!
We are implementing a new service which query directly to the API, this service consumes a very large amount of API resources and may be penalized normal operation of the frontend.

We had thought about separating the frontend installing new one

This would look like:

.- A server with Zabbix-server process
.- A server with DB
.- A server with frontend where it could be accessed by any user who is registered in zabbix.
.- A server where we would put a frontend server that only had access to servers will check the API, filtering it with a firewall. I could not access it in any way and would not have created users and would not be connected LDAP. Exclusive to the API.

It is possible to install two frontends pointing to the same DB?
Have you see a problem with this setup?


Thanks a lot!

[kloczek]

It is possible to install two frontends pointing to the same DB?

Yes

Have you see a problem with this setup?

No.

PS. I'm using in my test installation DSR LB (my setup is using Solaris ELB) with two web servers working behind LB. Only thing which is needed in LB setup is enable sticky sessions to LB settings as potentially updating users session data in tables may cause some locking issue or to avoid such locking you need to SQL engine in case using MySQL transaction-isolation=READ-COMMITTED (on Oracle AFAIK nothing needs to be changed because oracle engine is using transactions semantics similar to MySQL READ-COMMITTED.

Generally API GW problems are known to Zabbix dev team and trust me they are really hard working on prepare zabbix to start moving outside php code zabbix API GW. Few things needs to be reshaped in zabbix server process and the same preparations needs to be done in web frontend.
Zbx 3.0.x IMO is kind of preparation stage on implementing in zabbix server process API GW. However looks like now this feature still is not on top of the priorities for next stable version so if someone is not going to donate this task no one knows when it will be available (http://www.zabbix.com/development_services.php).
Remember that zabbix API interface initially was implemented as kind of JFDI