Zabbix 1.1 Beta8 on production system?

[korgano]

Hi all,

I have been experimenting with Zabbix for the last few days, and am thinking about using it for all monitoring purposes on our companies web- & mail-servers.

To do so, I would wipe my current configuration and start from scratch, having templates for the different type of servers and so on. Until now I have been using Zabbix-1.0 (have a debian-repo for that, which makes install/remove more easy). But since I have seen, what big improvements 1.1 will bring I am tempted to upgrade to 1.1-Beta8.

What big risks are there still in Beta8 or when is the final release planned? Will it be sufficient to only use 1.1 for zabbix-server (found a few forum-threads about old agents being compatible, is that correct?)? Is there a debian-repository for 1.1-releases?

Lots of questions
Thanks in advance for all the answers,
korgano

[edc]

Hi all,
Is there a debian-repository for 1.1-releases?

deb http://mirror.opf.slu.cz/zabbix unstable contrib

[korgano]

thx,

any expiriences on how good this works on a debian stable system?

[korgano]

Alright, I updated to 1.1B8, had some fighting with MySQL till I got the updates done, but seems to work now.

One question (didn't find anything related to it in the wiki):
How can I link a host to more than one template, or is there a possibility to build templates from other templates (merge ...)?

thanks,
korgano

[elkor]

you can't

templates can be chained together but that is all

you can have the following

basic_unix
debian
mail_gateways

and link them as such

yourhost -> mail_gateways -> debian -> basic_unix

but if you had a mail gateway running on say, slackware and only wanted the basic_unix inheritance you would have to create a new gateway template:

yourhost -> mail_gateways2 -> basic_unix

because mail_gateways is ALWAYS linked to debian after you create that relationship.

hope that's not too confusing.. think I confused myself

[korgano]

thanks for the answer,

I think understand, what you mean - but this way, it's very unflexible, because I can't even have more than one of the standard templates (e.g. Application.MySQL, basic_unix, ...), if I don't want it to automatically link to another one.

A good "workaround" for this would be, if there was an option to copy a template (or is there already a method for doing so?).

[elkor]

no, not currently.

and it's agreed that this approach seems unflexible but for software reasons, it's the path that alexei chose.

the good news is that once you do create your templates once you don't have to do it for each host (which was the old way of doing it before templating worked at all).