Bad documentation
Why is it that such a great project has such a horrible documentation?
The documentation for Zabbix v1.1 located at http://www.zabbix.com/manual/v1.1/ gives only
general guidelines to solve problems. And contains many faults.
My main problem however, is the actual content!
One example would be the Win32 agent. It is poooorly documented.
I had to browse these forums to locate some good info on it, for example it's items isn't documented. Now, I don't mind browsing a forum, but many users may miss such valuable information and be unable to utilise this great tool.
Also, what is the point of having a Wiki when it doesn't contain anything?
Under download there is a "manual". In .pdf? Come on, when I really need access to the documentation is
when I am at the console of a server, naturally without any graphical interface, thus no .pdf parser.
How about providing it in plain-text in the Zabbix-package? It is really impractical to have to lynx myself into
your website, and become frustrated by browsing through the thin documentation.
Now this reference manual, it's dated 23.04.2004, that's more than two years ago!!!
I suppose from now on I have to start inspecting the code itself to gain the neccesary information I need
to setup my Zabbix configuration.
Btw, it seems to me that many things are broken or has changed in Zabbix v1.1 without any notice to users.
Why is it that such a great project has such a horrible documentation?
The documentation for Zabbix v1.1 located at http://www.zabbix.com/manual/v1.1/ gives only
general guidelines to solve problems. And contains many faults.
My main problem however, is the actual content!
One example would be the Win32 agent. It is poooorly documented.
I had to browse these forums to locate some good info on it, for example it's items isn't documented. Now, I don't mind browsing a forum, but many users may miss such valuable information and be unable to utilise this great tool.
Also, what is the point of having a Wiki when it doesn't contain anything?
Under download there is a "manual". In .pdf? Come on, when I really need access to the documentation is
when I am at the console of a server, naturally without any graphical interface, thus no .pdf parser.
How about providing it in plain-text in the Zabbix-package? It is really impractical to have to lynx myself into
your website, and become frustrated by browsing through the thin documentation.
Now this reference manual, it's dated 23.04.2004, that's more than two years ago!!!
I suppose from now on I have to start inspecting the code itself to gain the neccesary information I need
to setup my Zabbix configuration.
Btw, it seems to me that many things are broken or has changed in Zabbix v1.1 without any notice to users.


Comment