Over the last few months on and off I’ve been working to deploy Zabbix to the fedora infra staging. I’ve received a lot of help from others along the way, and we now finally have a working instance ready to be tested .
Awesome work. Thanks for doing this!
It’s hooked into the Fedora FAS system for authentication, however there is one caveat. This version of Zabbix requires that a user be created on the Zabbix side. So until that is completed you won’t actually be able to login.
I’m considering creating a
sysadmin-zabbix group membership as to who has accounts created/read only access, while edit/admin access will be reserved for
Does zabbix have anything like a ‘guest’ view? With nagios currently we
let anyone look / read-only and thats sometimes helpful in see when
things are broken, etc.
Actually, looking at it we allowed any valid user to login, but just
didn’t give them privs to ack things/supress alerts/do anything.
Perhaps we could just reuse the sysadmin-noc group here? (for the lower
access that can ack/etc) and main for the admin access?
I think I saw that the next major zabbix version should allow creating
accounts automatically, so perhaps we just don’t worry too much for now
and move to that version when it’s out/we can?
There are 2 ansible roles for deployment see , zabbix_agent (should auto enrol hosts with server) and zabbix_server (covers deployment of zabbix server itself). The server is running RHEL9 and its running Zabbix LTS 6.x. I went with postgres db running locally on the same machine.
Sounds good. We do have a generic db server, but perhaps in this case it
might be better to be self contained to avoid the dependency on that
server being up/working.
I’d like to invite interested folks that want to come take a look, poke the tyres make themselves known, I’ll create an account on the zabbix staging server which you can then login via your FAS account at . If you have feedback/suggestions regarding the deployment etc nows the time to make them while I have cycles to action it!
Awesome. I poked around a bit, but not too much yet, will try more next
I wonder if we couldn’t roll the agent out to the rest of .stg. soon?
Might be nice to get more hosts in there and confirm that the agent
Once everyones happy, I’ll go ahead with a production deployment, and begin rolling the zabbix agent out to all hosts. Lot of work to be done to start replacing the nagios monitoring with Zabbix equivalents, so potentially plenty of small pieces of work people interested in contributing might be willing to take on!
There is a zabbix ansible collection. We may want to look at pacakaging
that up and using it to configure things? I think the base agent stuff
is probibly good for much of what nagios does, but the ‘special’ checks
may have to be implemented in ansible, etc. I’m not sure if the
collection does this kind of thing or it’s more base config, but we
should look into it.
We should perhaps look at rolling to prod after f39 beta freeze, or
after f39 is out. Then we can run both zabbix and nagios for a while and
migrate things over. I’m sure there’s stuff we have added to nagios over
the years we need to reimplement in zabbix.
One of those that leaps to mind would be the ability to send alerts to
our matrix channel (or some subset of them). I’m sure we can figure
Anyhow, thanks again for moving this forward!