Zabbix as of late delivered the new 5.2 rendition with magnificent new highlights outlined in the video, for example, hashicorp vault, IoT monitoring, further developed execution, granular authorization framework, and substantially more.
The move up to the most recent Update Zabbix Server is quick and simple. In this tutorial how to redesign Zabbiz server 4.0 to 5.0 utilizing Ubuntu 18.04 server. You can follow this step for your nearby server or public server for update zabbix server rendition 4.0 to 5.0 or most recent.
This is a vital step. Ensure that you have a reinforcement of your data set. It will help assuming that the update methodology comes up short Update Date of Exit in EPF Online. Rather than basically keeping the old zabbix-server.conf, it would be smarter to keep the upgraded one, and move your old settings into the new config record. That way you the design document stays in a state of harmony with the zabbix form.
Find out wany mistake from log document, I see data set name, client name and secret phrase not match. That is the reason can’t interface with information base utilizing my old client secret key. I think Update Zabbix Server record supplant utilizing default settings.
Overhaul Zabbix on CentOS 8
To overhaul the current Zabbix example introduced on CentOS 7, it is prescribed to relocate to CentOS 8 first as presently there are no authority bundles accessible of CentOS 7 for Zabbix 5.2. Since there is no perfect method for overhauling CentOS establishment, it is prescribed to make another server on CentOS 8 and afterward relocate your data set and twist up Zabbix Server there.
CentOS 7 is old and has restricted bundles in the repositories, which are not updated any longer. Regardless of whether you utilize all the most recent programming and bundles from the authority repo, it won’t be sufficient to effectively run all of the usefulness of Update Zabbix Server . For example, TLS 1.3 won’t be accessible, as well as information base encryption.
Assuming you run the default frontend and default server from the bundles, and on the off chance that you have no customization fixes, any custom usefulness, or altered PHP source code that you need to save, then the redesign is direct.
New in Zabbix 5.2
To figure out what we can anticipate after the overhaul, on the Update Zabbix Server page for the 5.2 delivery, go to Establishment > Update notes for 5.2.0.
- The base required PHP form has been increased from 7.2.0 to 7.2.5, which may be an issue on CentOS 7.
- Client jobs. Presently you can allot various jobs to your current clients through your current authorization framework won’t be broken.
- Time region definition. Assuming that you are running your frontend with numerous virtual hosts, you can erase those and design everything locally in the frontend.
- Invigorating unsupported things setting has been eliminated from Organization > General > Other, with the thing update span presently utilized for each unsupported thing.
- Layout screens changed over completely to dashboards with the screens to be set up in the dashboards now as gadgets of format dashboards.
- The meeting of the Zabbix frontend is presently stored in a treat.
Assuming that you overhaul, you will in any case need to sign in to the frontend giving the username and secret phrase.
This was everything expected for the establishment to run effectively. The cycle is direct on the off chance that you have no muddled customizations of your frontend, Update Zabbix Server , and so forth. However underway, it is prescribed to test establishment out in the dev climate and make reinforcements.