Which version to use and if any vulnerabiltiy

[Abinash]

I am setting up an enterprise level project and want to use zabbix as monitoring tool.
i am confused b/w 7.0 vs 7.4 , which version to use.

I am using two servers for monitoring and using mariadb galera as a database and a galera arbitrator for quorum vote.
I am using keepalived and rsync process.

Kinldy suggest me any other information to make it more better and robust.

Also is there any vulnerability or loop hole in the code of zabbix that can be a threat for an enterprise level, as i am new to the tool.

[cyber]

.0 versions are LTS versions, they are supported longer than intermediate ones.. https://www.zabbix.com/life_cycle_and_release_policy
Security related info can be found https://www.zabbix.com/zabbix_security_policy also security advisories are available https://www.zabbix.com/security_advisories

[Abinash]

Thanks for the reply, can you help me with the High Availability part for 2 servers where i want to install zabbix 7.0.

i want that both the servers should have zabbix 7.0, and it should work as HA, but the database should alwyas be in rsync .

can you suggest some good approach.

Currently i am using :

mariadb Galera and Arbitrator,
Keepalived
VRRP.
zabbix 7.0 as monitoring tool .
Kindly help me with some good suggestions to make it enterprise level

[irontmp]

I am setting up an enterprise level project and want to use zabbix as monitoring tool.
i am confused b/w 7.0 vs 7.4 , which version to use.

I am using two servers for monitoring and using mariadb galera as a database and a galera arbitrator for quorum vote.
I am using keepalived and rsync process.

Kinldy suggest me any other information to make it more better and robust.

Also is there any vulnerability or loop hole in the code of zabbix that can be a threat for an enterprise level like men widow’s peak styles, as i am new to the tool.

Go with Zabbix 7.4 if it’s available and stable in your repo, since it will include newer fixes and security improvements. Your setup already looks solid with Galera + arbitrator and keepalived. Just make sure DB performance is tightly monitored, and consider using Zabbix proxies if you scale or add remote locations. Also enable TLS between components and keep regular backups outside the cluster. Zabbix is generally safe for enterprise use. The main risks come from outdated versions or poor configuration, not inherent flaws. Keep it updated, lock down access, and follow least-privilege practices for users and API.

[Abinash]

Thanks for the reply!!

Can you let me know if zabbix 7.0 is also suitable in my scenario, as its support time is 2029, where as for zabbix 7.4 is end of 2026.

If you could let me know.

[cyber]

Depending on your pain level. I would go with LTS-es in bigger environment.

[Antimidas]

Abinash - I wrote a guide on how to configure MariaDB or MySQL for HA where it keeps the database updated between servers. I use Pacemaker and Corosync. A similar process is followed to configure three servers for DB, three for the Zabbix Server, and 3 for the Zabbix front-end. The guide is at https://antimidas.net/?p=16. It has served my purpose for about 4 years without any incidents.

[Antimidas]

I have had a couple of issues with my site being publicly available. I am ok with that because I am the only real user of the site. It is more for my notes to recall how to do things in case I ever need to repeat them. Here is the relevant excerpt that will give you some excellent resources.

These instructions are based on a very well written resource by Markku Leiniö. The original source document can be found at https://majornetwork.net/2020/01/hig...bix-on-debian/. In addition, I have incorporated information from Edmunds Vesmanis from a presentation he gave at the Zabbix Summit 2019 in China on setting up HA clusters for use in Zabbix. That source presentation can be found at https://assets.zabbix.com/files/even...ter_setups.pdf. There is also a video presentation from the event at https://www.youtube.com/watch?v=vdoUWkwk9QU. Both authors are worth the read and use slightly different approaches. I have opted to follow Markku’s approach of using GTID for replication because it is easy to follow and works for my situation.