Zabbix Frontend only in read access on the DB

[Matthieu]

Hi,

I have just a question, is the frontend needs to write in the db? I ask this question because I have 6 screens that show zabbix data at the same time and this increase the request on my mysql DB.
Is it possible to bind the frontend on a mysql slave?

Thanks,


Matthieu

[ghoz]

The frontend stores sessions state and audit data (who logged in) in the db,

So the answer seems to be 'no'...

[nelsonab]

The frontend stores sessions state and audit data (who logged in) in the db,

So the answer seems to be 'no'...

That being said you could configure your "viewer web-servers" to use a different DB account to connect to the DB which does not have write access to every table, just the session and audit associated tables. That way if someone got around the internal Zabbix permissions they still wouldn't be able to edit any of the items, as the DB would not allow writes to the items, history and whatnot tables.

Just a quick guess I think you'll need access to audit, session, and user (so the webfrontend can write last login I think)

[Matthieu]

Ok, thanks for your response, I can throw in the trash my idea to bind the frontend on mysql slave.

Regards,

Matthieu

[ghoz]

Nah, could be interesting to add a feature request in the tracker...

you could also test adding a mysql proxy for your frontend, redirecting writes to the master and reads to the slave...

not sure how it would fare however...

[Matthieu]

humm nice idea. I'm going to test this solution and I will give you a feedback

Matthieu