Beta1 and Beta2 are severely broken, which alpha version is most stable?

[illumin8]

Zabbix is a great product, don't get me wrong. I've been using it since v1.0 and more recently have been using alpha 10 in a production environment. It's been extremely stable.

I'm now implementing a new Zabbix solution and wanted to use the latest beta2. It seems to have some great new features that would allow me to keep inventory of my systems and track much more information about each system which is nice, but the ^%&#@&$ templating system is broken as all hell.

Templating was the nicest part of Zabbix alpha 10, and it worked beautifully. Now it doesn't seem to work at all.

I could manually add the items and triggers, but now the overview screen shows a million different rows. I need it to show one row for each trigger, and all the hosts that have that trigger in columns.

I don't even mind manually manipulating the MySQL database to do this if necessary.

So, since beta2 is hopelessly broken, which version is actually stable enough and has working templates? I would like to know which version I should roll back to to get working templates.

Thanks for your help, and here's hoping the beta versions get fixed soon.

[Alexei]

I take the template-related problems very seriously, actually this is main focus of coming 1.1beta3 release. Please, be patient, wait for 1.1beta3, it will be released in a week time.

[jpawlowski]

is there already better stuff in the current cvs? i would try to use it if there are important changes that should solve problems releating templates.

[Alexei]

I wouldn't use CVS, as it contains new pieces of not-carefully-tested-yet functionality.

[illumin8]

I take the template-related problems very seriously, actually this is main focus of coming 1.1beta3 release. Please, be patient, wait for 1.1beta3, it will be released in a week time.

Thanks for the response. I'll patiently wait until beta3 to get things really rolling with my monitoring solution. I appreciate all of the hard work you put into this project Alexei.

[Wolfgang]

Thanks for the response. I'll patiently wait until beta3 to get things really rolling with my monitoring solution. I appreciate all of the hard work you put into this project Alexei.

I totally agree - Thank you Alexei

[edeus]

Does the templating come from the frontend and if so, does this mean it would be "safe" to cvs just the php? Frontend shouldnt have any major problems I hope.

Nevermind, I better just wait.

[nesvarbu]

I take the template-related problems very seriously, actually this is main focus of coming 1.1beta3 release. Please, be patient, wait for 1.1beta3, it will be released in a week time.

Week kind'a passed already? Is it enought to download frontend from CVS? Templates would really make our lives much more easy Thanks for you work Alexei

[James Wells]

Greetings,

The template functionality is not currently working in the CVS repository. The UI from CVS is fairly safe to use at present, however, please keep in mind that we are still doing development work on the UI and as such some of the functionality that is there is going to be altered before the release of 1.1beta3.

Additionally, please note that there are DB schema changes in 1.1beta3 that may cause issues with the 1.1beta2 server. Mind you, I am running 1.1beta3 UI and the new DB schema with the 1.1beta2 server without issue, but your mileage may very.

[KarmaPolice]

Any ETA on beta3? I'm looking at rolling this out live in about 2 weeks and would like to know if i should plan on having beta3 or rolling forward with beta2?

Thanks for any info, i know it's always hard to answer those questions.

Cheers

[edeus]

I'd suggest rolling out with whatever is available:-

Make sure there is some facility for an easy upgrade path. I have automatic upgrade scripts for zabbix on servers should a new version come out. With testing, this has saved a lot of time.

[onslo]

Update ?

Any further news on beta3 yet?

I really need templating to work before I can roll out on my network.

Regards

Onslo

[elkor]

Patience guys, they are working on it.

If you are really itchy you can always pull the current frontend from cvs and plug the holes yourself ;-)