Feature request - Integrated knowledgebase

[cybaspace]

We are using Zabbix extensively to monitor 200+ hosts with a few hundrerd triggers. At night we have night-operators monitoring our systems. We want to let them use zabbix too but the problem is that when they see a trigger become true, they don't know what to do. Wouldn't is be a nice idea to link a trigger to some kind of basic knowledgebase where the possible solutions are described.

I know that it is already possible to put some info in the comments but it would be nice if operators can search and browse through such a knowledgebase.

Keep up the good work! We all love Zabbix over here and we can't live without it anymore!

[Alexei]

Any idea how this can be implemented? You may already use an URL in trigger definition form to point a trigger to some external location (think Wiki). Is it exaclty what you want?

[cybaspace]

Sort of. I already did it by putting a link in a trigger to a phpknowledgebase page. This works ofcourse, but it is a lot of work to maintain 2 systems (zabbix and a seperate knowledgebase).

It would be nice that when you add a trigger, that you can fill in a 'possible solution' field. And when the trigger becomes true that you can click on an icon (a brain for example )so you can see the possible solution to make the trigger false. It would be nice also if you can search in this knowledgebase.

It doesn't have to be verry fancy, just a plain solutions database in wich you can find awnsers to problems.

[ghislain]

oh nooo

Then why not integrate you text in the action description or trigger description, where is the need for another field in the DB ?



i think that adding little knowledge base is not needed.

You can add to a trigger description a link to a FAQ system, plenty exist that could suit the need easely.

Remember that this kind of thing would allready be implemented on lot of organisations. Real monitoring means:

- ticket system
- faq
- support pages

etc... at least..

All this must be the surroundings of zabbix so it is thinked in a way it can be integrated (for exemple, modular login that permit authentification to ldap or external system for auth). Things like scripted trigger are a good exemple on how to setup zabbix interacting with other systems.

Adding basic function like this IN zabbix will NEVER suits the need of more than 10% of people at a time. Let zabbix be a powerfull system that integrate well with others.

For me a partnership to have sort of bundled interraction between zabbix and another project like phpmyfaq could be done but would be the farest it is advised to go. With a public interface to any link done with that particular external FAQ or other so anyone having a similar app can integrate it by writting a few lines.

I advise for a strong product able to integrate in an IT environement rather than an integrated blob of functions that will lacking things everywhere as nobody can put ressources in each part like otrg or phpmyfaq does for their own.



This is only my two cents of course

regards,
Ghislain.

[raminix]

Excellent point. Zabbix is an excellent network monitoring and data collection tool. There are excellent knowledgebase/wiki/CMS systems out there as well. Why reinvent the wheel? Adding a bunch of fringe, non-essential functions that can be accomplished with already existing tools will only result in the dilution of an excellent tool - Zabbix.