The only Alexei Vladishev

[ruckus37]

Hi Alexei

Great programming, this is a great example of how monitoring should be done. I have had my problems from the beginning, the early days of zabbix waiting for a patch, and you have exceeded my expectations, just recently I figured out triggers and actions in beta5, working nearly perfectly. OK the question, I have my monitoring software (free{and weird, where do you get your income} ), when you die, pun we all die or give up hope at some stage, can we carryon without zabbix? I will probably die before you but just too make the bosses happy, “What do we DO”,.

Option 1.
Invest in a new system and import trends – easy, just need $$$

Option 2.
Get hold of your best friend and have him dig up the code and have him/her explain it.

Option 3.
You have a plan.

Again thanks for the software, my life is much better since Beta5, keep it up.

Thanks
Ruckus37

[edeus]

Point1. I thought there was a team developing this?

Point2. Are you not "all there" with the theory behind Open Source? It's Open to all, no digging tools necessary! (+licensing issues if any)

Point3. What a strange thing to post... but it is on the minds of a lot of managers I know.

[Alexei]

Don't worry. It is freezing cold (-25C) outside these days, but I'm looking forward to survive By the way I'm working on ZABBIX full time.

[DiedX]

Don't worry. It is freezing cold (-25C) outside these days, but I'm looking forward to survive By the way I'm working on ZABBIX full time.

/me bows

BTW: This project is working like a charm, AND is OSS (Open Source Software), so further development will not be a problem.

[ruckus37]

OK,but OS projects do not mean that there is always a person on hand to solve problems that may need am immediate patch. You cannot rely on the OS community to deliver, the zabbix team has been very good so far (from an open source perspective), but this project could die at any time and thus the enthusiasm for this project (I hope not) .

[KpitaoKverna]

ruckus37,

I don't understand your point of view. But if I could understand your problem, listen.

If you need a instant patch to solve your problem, you have 2 options.

1 - Believe in Zabbix as the best monitoring tool and make the patch, send to Alexei and make Zabbix stronger.

Or

2 - Buy a high cost monitoring tool with suport included and demand your patch to then.


Zabbix is Open Source.
Alexei is the "development team", however nothing says that you cannot help.

Open Source are not only Community Development
And I understand why Alexei makes the development closed, many hands working on a huge project like this will make a lot of security hole, bugs and trash on the code.

I hope you can understand my point of view.

Hugs
Felipe Duran

[ruckus37]

Hugs too you to Felipe Duran

My point of view is very simple:

Zabbix is a first-class monitoring application

My problem was convincing the rest of our IT-department to implement it. They also share my enthusiasm for the project after a short demonstration but there is always the party breaker that has a narrow view on open source: hence my pervious questions. Well my final verdict was :

“Zabbix is a fundamentally sound application that lives up to our expectations and we should use it as long as Zabbix lives.”

I pointed out that Zabbix is under development and that the “development team” provides regular version patches. If at some stage Zabbix is not an option anymore we will take appropriate action at that time. We can always have that version of Zabbix running as a history reference for trends or export the data to some reporting software. (Probably not in my lifetime).

We are using Zabbix today and will probably continue for a long time. There is always the COMMERCIAL SUPPORT GOLD option, if things get out of control.

Anyway thanks for the replies,

Ruckus37

[Alexei]

I would like to stress several points:

1. Currently we have a team of developers working on ZABBIX full time and we are hiring more: www.zabbix.com/jobs.php

2. One can always buy ZABBIX commercial support which guarantees certain level of service. Contact [email protected] if you need more information.

3. Our patch policy is not to limit creativity, it is all about quality. Honestly 95% of patches I have accepted turned into bug reports. It is much easier for us to develop something from scratch and according to our coding standards rather that make a full code review and testing of a proposed patch.

[Markus]

The only Alexei Vladishev

ruckus37,
2 - Buy a high cost monitoring tool with suport included and demand your patch to then.

Even worse, paid support will most likely not cover having your individual patches integrated into a product. You would have to pay _lots_ of money for a customised version and only _if_ the vendor has some member of the development team available. Unless you are a major customer of theirs, simply forget it!

With Open Source you always have the option to program an individual extension yourself or make suggestions for features on a forum like this.

Markus